Seems useful.<p>TL;DR on my questions:<p>- API<p>- Leverage tooling for infrastructure monitoring<p>- Clients (Python, or others)<p>- CLI<p>- Hooks (launch scripts on events)<p>- Events abstraction to connect different systems (cloudevents.io)<p>- Groups<p>Have you thought of treating it like events in production and leveraging monitoring tools for humans? For example, we do work with events to monitor infrastructure and trigger actions, but that is what many of us do for a living, and not usable by most people.<p>You can have a "Human Reliability Engineering". If you bring the tooling to monitor infrastructure to regular folks, that could be something. Because then you can leverage tools with common abstractions and language (metrics, events, etc.) You can then leverage Grafana, Prometheus, Elasticsearch, and all the tools that do that very well for infrastructure.<p>Speaking of abstractions, have you checked cloudevents.io[1]? You can then open yourself to various protocols and destinations that understand these events, and people could build applications <i>on top</i> of your service.<p>Also, have you thought of opening the API and adding a client or CLI so people can control it without opening the mobile app?<p>For example, as a user, I could generate API keys from your site and then use these keys in a client (Go, Python, whatnot) to pretty much do anything I could do with the application, get data, push data.<p>Also, have you thought about adding hooks so I can write a program that says: whenever I add an event, run scripts in certain directories. Similar to Git hooks.<p>The script is executed with the event as an argument, and does whatever I want it to do. It can be as silly as the following:<p>I add an event of drinking a cup of coffee. There's a script that gets that event, and decrements a counter somewhere of coffee capsules, and if the coffee capsules are under a certain threshold, trigger an alert or something.<p>If there are groups, I can have a hook that alerts several people in a group that we're out of coffee.<p>This may be useful for people recovering from an addiction, for example. A group trying to quit a certain substance. Every time a member of the group consumes said substance, it triggers an event.<p>They could monitor themselves, but they may also monitor each other and see that member A is doing fine, but member B is starting to drink more and more this week. What's going on? Let's check up on them, talk with them, support them as they may be going through a rough one.<p>Someone more experimented could see _patterns_ of events. Substance consumption, missing workouts, increased spending, etc. Is there disengagement?<p>Once you generate that data in a standardized way that can be leveraged by mature tools, people can build things on top of it and you can get many ideas and use cases.<p>[1]: <a href="https://cloudevents.io" rel="nofollow">https://cloudevents.io</a>