I present: safe://checklists.
The idea is that on the first screen you can create checklists and view lists that you have made previously. Clicking on one of the lists takes you to that list, where you can create entries and check them off as they are completed.
The way it works behind the scenes is that every time a change is made, the state of the app is serialized and saved in a mutable data entry. This is the same way that @draw’s safe://todo app works, so thanks to him for doing the heavy lifting there.
Speaking of safe://todo, the most interesting feature of my app is interoperability with that site. When safe://checklists loads, in addition to looking for its own data, it also looks to see if the user has a data entry from safe://todo. If so, it creates a list on the home screen which ties directly to the same list that you see on safe://todo. When you modify that list, it is saved to the data location used by safe://todo. So you can make changes on one site, then see that change reflected on the other site when you refresh. This is a simple example of users maintaining control of their own data on the SAFE network, as opposed to having their data locked away in a data silo provided by the application vendor. By using common data formats, the user’s information can be presented and manipulated by different apps, giving much greater freedom and flexibility to the user (no lock-in to a specific provider etc).
troubleshooting: if you have any trouble with the app, right click on the page and go to ‘Inspect Element’, then click on the ‘console’ tab and send the log that you see there to me via DM.