At some point it would be nice to present potential developers with a less ‘contrived’ demo; ‘todos’ isn’t the best IMO, but I’m hoping it’s a useful step in that direction.
Odd, updating todo items in that app is giving me a lot of issues right now, but I tested it extensively when I refactored the code a while back. Unfortunately, I don’t have time to look into it until the middle of next week or so.
a demo of these apps in the same window so that syncing can easily be observed.
something like this might be helpful for newcomers to understand what it means to connect your storage and have other apps use it. and maybe useful for debugging purposes.
A simplified podcast player always seemed to me to be the best fit to demonstrate how remoteStorage, Solid pods, etc. can be put to use.
Just like the quintessential use case for the Web turned out to be an encyclopedia that somehow managed not to materialize until a decade after the Web was invented, there’s still time enough for advocates of the “personal data store” concept to produce a compelling (but feature-limited*) in-browser audio player that keeps your subscription list and episode playback position in user-controlled storage.
* taking a page from Peter Suber on the design of the initial rules for Nomic—where the default scoring mechanism is so uninteresting players will feel motivated to immediately change the game to better suit them
Not really what I meant; apps like those and many others would benefit from integration, but those two are apps in their own right with opinionated choices in UI (and implementation) and not really good for pedagogical purposes.
If a block of sample code meant to demonstrate how a library works doesn’t have any recurring daily users, it doesn’t matter—there are no unmet expectations. It’s sample code.
A codebase that doesn’t have as its foremost concern serving as an example to learn from because it instead concerns itself with the ongoing development/maintenance of an app designed for widespread real-world use, that’s going to be less helpful than sample code that knows it’s purpose is pedagogical. The evident concerns from reading the code aren’t going to be about the simplicity of the code or whether people find it easy to understand and incorporate its ideas into apps of their own. Development will be driven like the development of any other app where the point is for the end user (whether programmer or not) to evaluate its UI and featureset and choose or not choose to use it on that basis.