stts 2.0

[inket]

• [x] Use JSON definitions for services instead of classes

  • [ ] Document adding services in README, and defining own services

---

• [ ] Rethink "categories" and "sub-services"

  • No need for a different class/model for each sub-service. Only display the main service but take user preference of sub-services into account when displaying status.

  • Store user selection of sub-services as a dictionary "<globalIdentifier>": ["<subIdentifier>", "<subIdentifier2>"]

---

• [ ] Create a new editing UI, leaving the status bar popup to only contain the list of selected services

  • Sidebar: Services, Settings, About

  • Services: 2 columns, one for services, and a second for the "sub-services" which are loaded at user request - but also a button to open Application Support for dropping a custom services.json

  • Settings: Same, but add more if necessary?

  • In popup, add a 3-dot button next to each service that appears on hover to quickly jump to the settings for a service

---

Maybe 2.1?

---

• [ ] Host a services.json on the web and load it from the app to require less MAS updates

  • [ ] Use app-logic for a server-side swift app that checks that all service-checking APIs are responding fine

  • [ ] Also update privacy policy

---

• [ ] Add general check services support (the 200 = OK kind), that can be enabled via the custom services.json in Application Support