Download websites that use Sencha Touch

About Sencha Touch

Before the app stores settled the argument, a great deal of engineering went into the belief that mobile software would be written once and delivered through the browser. Frameworks of that period tried to make a web page behave like a native application, with momentum scrolling, list views, sliding panels and toolbars that did not feel borrowed from a desktop, and for a few years that looked like the sensible bet.

Sencha Touch came out of that moment, built by Sencha Inc. in JavaScript and filed under JavaScript frameworks, with records in our data from 2010. Its recorded license is GPL v3, a copyleft license, which matters for detection as much as for procurement, because source that can be copied freely tends to be vendored into an application's own bundle rather than loaded from a vendor's servers.

So a live match today points at an application written for that era and never rewritten since. In practice the survivors are internal portals, field service tools, dealer and partner systems, kiosk interfaces and public sector applications, the places where the audience is captive, the interface only has to keep working, and the cost of a rewrite has never cleared the bar. Consumer facing sites moved on a long time ago, which is exactly why the remaining population is interesting rather than negligible.

For a researcher, a front end framework detection works as a dating method. Combined with server side signals it identifies organisations carrying front end debt, which reads as an opportunity to an agency selling modernisation and as an exposure to a security team, since an unmaintained framework arrives with an unmaintained dependency tree and no upstream fixes for anything discovered in it since.

As of October 2026 we see the framework on 4 sites. Undercounting is expected for the reason the license implies, since a copy minified into a bundle or renamed during a build will not match a fingerprint keyed to the stock file layout, and the hosts that do match are the ones that kept the original structure. The figure is a floor, and the population skews toward the least modified installs.

A copyleft license also changes who can be found at all. Commercial frameworks leave a trail of contracts, and a vendor knows its own customers. Anything that can be downloaded and shipped without asking permission leaves the vendor with an incomplete picture, and an external crawl becomes one of the few ways to observe the deployed base. The detected population and any vendor customer list are simply different sets, and for questions about where a framework actually ended up, the crawl is the more honest source of the two.

What the list answers is the question a lookup cannot. Whether one domain runs the framework is a single check anyone can perform. Which organisations still run it, what they run it beside, whether they cluster in particular sectors, and whether the set is shrinking are questions that need every match in one file, and that is the form in which this kind of data is worth paying for.