BobDickinson
commented
10 years ago If "seed" endpoint present in seed.json asset, MaaaS app at the endpoint is launched when MaaaS client is run (this is how real pre-built clients will work).
If not, there is a launcher interface with a list of MaaaS apps, and the ability to add (by "endpoint"), launch and delete.
The above is working on all platforms.
Ability to back out of MaaaS app (back to the launcher) is inconsistent at present (there isn't exactly a concept of the "top" of MaaaS app navigation to know that back from there should go to the launcher, if the app was launched by the launcher). Still thinking about this.
Storage of app "state" (session id) not yet implemented (pending implementation of persistent server state implementation so we can test).
Main page:
How do we get out of a Maaas app and back to this main menu (since app top pages don't have 'back')? Secret gesture from app top page? Any page?
State should be stored per-app (session-id is probably all, maybe current page id, maybe resource cache when we have that). Requires persistent client state mechanism on server for this to actually be useful.