Typescene offers a component model that goes beyond UI rendering, and supports comprehensive state management out of the box. Other than a build chain (Webpack, Parcel, or otherwise) there are no dependencies to worry about at all.
All it takes to get started with Typescene is a single command. From there, the intuitive object-oriented architecture makes it easy to scale up simply by adding the components you need.
Activities represent the underlying application state, reflecting how the user sees your app. These provide data to views and handle input events. Each view is bound to one activity, but multiple activities can be active at the same time since they can be nested and routed independently.
Services contain data that isn’t tied to a particular activity, and provide access to the global state. Services are great for encapsulating database access, login sessions, and user preferences, so that they can be used from any other component using just their name.
Learn more about Typescene’s architecture here.
Q. Who makes Typescene? – A. Typescene is an independent open source project. It was originally started by a single developer around the same time as some of the big frameworks that are around today. After years of polishing and dog-fooding, code and tools have been made available for general use.
Q. Should I use Typescene for my next app? – A. Sure! Read the documentation and use the guides to familiarize yourself with the framework and get started.
Q. Should I use Typescene for my website or blog? – A. No, probably not. Typescene was developed for interactive applications that resemble desktop or mobile apps, not server-generated content.
Q. Does Typescene include a calendar / pagination / tag cloud / other UI widget? – A. Not the main package, no. The aim is to include only ‘primitive’ components, which can be combined into other components and published as separate NPM packages.
Not convinced? Read more about Typescene’s design goals.