The default mode for Fission apps is more like native mobile or desktop apps: a single user is logged in and editing / operating on their own data. Their own file system can be used as a database.
This scales to 10s, 100s, or 1000s of users all using the same app, executing on their local machine, and working with their own data.
But it means that Aggregate Data Views work a little differently. We’re going to define two different types of these aggregate views:
Multiple people with Fission accounts who share data with each other.
This is the standard, logged in, collaboration use case that most multi-user apps function as.
It also leads to very dynamic interfaces, like real time editing or other collaborative tasks.
We will provide this in the SDK alongside group access control, making it easy to build these types of collaborative apps, in a way that evolves from the single user app style.
This is when an anonymous / not logged in user visits a web address, and can see (dynamic) data from multiple people.
Two examples from the early apps we’ve got here:
A public view of quotes that users have tagged as public for Quotes App, perhaps at
A global high score leaderboard, eg. for a Tetris clone written in Elm
Some public views might be appropriate to publish statically. But that leaves out a lot of features. We want the app to have access to data so that it can be shared / shown publicly.