(The last time I tried something even remotely similar to this was December 2015, and it was more like...a to-do list, than a proper development plan.)
A lot of similar projects that have been inspirations for this one do something similar, and I enjoy reading their roadmap (and roadmap-review/postmortem) posts, so I figured, what the hell? Why not give it a shot?
Best-case scenario, this gives me a rough plan that I can use to stay motivated/focused on the important priorities from release to release. Worst-case scenario, I look back at this in a year and say, "man, what the hell was I thinking?"
The bullets beneath the headings are in no particular order (and certainly not in chronological order).
Everything under "Major Priorities" is going to get done before January 2019. Items under "Minor Priorities" are "maybe, maybe not" type items: I would like to get to them, but I might not.
- Finish the Settlement storage upgrade project.
- Publish version one of the API and version three of the webapp:
- fork the API out of the kdm-manager repo and create a new project for it
- "finish" the legacy webapp (i.e. completely remove everything, including session-management) and move it to V3.
- Revise the Campaign Summary's survivor "quick view" to work better during showdowns, e.g. to include hit boxes, armor point management, etc.
- API: get settlement serialization times down so that the average is five seconds or less
- Enhance iOS support for iPhone7/8 and iPad
- API: user notifications support.
- Implement GraphQL, at least as a trial/demo/beta.
- API and webapp: re-do timeline controls. Tear it all down and start over (because it's a disaster).
- Add unit testing to the API.
Minor Priorities / Backlog
- Develop gear grid support (probably as a beta first).
- Finish developing the Hunt Deck helper app (or kill it: could go either way).
- User-level, cross-settlement stats.
- Replace Twitter as the in-app alerts provider: add "admin message posting" to the API control panel (and link them into user notifications, some how).
- API: export to PDF, probably to one of Logan Ogden's revised spreadsheets
- User-specific, all-survivors stats-modification operations (e.g. Manhunter-style "set everyone's survival to zero" type stuff)
- API: enhance documentation by adding a self-creating "map" or diagram.