some kind of a digital asset • Sometimes there are overlapping (lack of knowledge of what other unit has done) • Usage monitoring and governance • Many stakeholder involvement in an asset’s lifecycle • Monetization options ?
(Why only apps ? Why not anything ?) • Ships with Three types of assets OOTB (Gadgets, Web Sites and E-Books) • Ability to add new types of assets and configure • Ability to extend the base functionality (subscription / payment process integration)
a new Resource Extension Type (RXT – a concept inherited from WSO2 GReg) • Add relevant jaggery pages to customize the asset based operations (Download vs Subscribe vs Bookmark) • Define the Asset LC in SCXML
and the back- end • Uses technologies such as jaggeryjs, caramel, handlebars • Modular to its core – any part of the store can be over ridden by dropping a relevant script in extensions • A team of geniuses