major_todo_app

An app that helps you get things done

Roadmap

This is just a loose feature roadmap right now, Soon we'll want a real release/lifecycle roadmap

Road to 0.1.0: The "Janktown" MVP

• Basic ad-hoc tasks (creation / completion)
• Task Stopwatch
• Hide completed items after X hours
• History page (wit details like duration, created)
  • bottom nav + new page
  • an "all tasks" query
  • listing tasks

0.2.0: Deployment

• Complete Google sign-in integration
  • Tables
  • jwt validation
  • login screen
  • micimize/major#10
• Set up testflight / CI

0.2.5: Design

• Basic design work (sketch)
• Implement Designs

0.3.0

• Visualizations / "serious" Quantification
• Task "Ongoing / Partially complete" concept (richer bullet journal carryover)
• Task Notes
• Import/Export format
• CLI? Web version?
• copy / paste? possibly task templates?
• structured tasks / grouped tasks: considerations: do tasks complete along with their constituent parts? should the be implemented recursively? Or a seperate concept

Structure

tree -L 3 -d -I 'node_modules|ios|android|build' .
.
├── act # scripts for ops stuff like testing actions and instantiating the db
├── app # the flutter app
│   ├── lib
│   │   ├── history  # submodules likely not current
│   │   ├── stopwatch
│   │   └── task_list
│   └── test
└── backend # postgraphile backend adapted from graphile/starter
    ├── @app
    │   ├── __tests__
    │   ├── config # shared configuration handling
    │   ├── db     # graphile-migrate based schema authoring
    │   ├── server # graphile server + firebase auth handling
    │   └── worker # disabled background worker (graphile-worker)
    └── data # output dir for schema info.

notes

• app/ios/Runner/GoogleService-Info.plist is required but contains an api key

operations

to init db:

# terminal 1
cloud_sql_proxy -instances=${DATABASE_INSTANCE}=tcp:2345

# terminal 2
cat act/database_superuser.env
DATABASE_SUPERUSER_PASSWORD=abc

cat act/secrets.env
DATABASE_INSTANCE=cloud_sql_connection_string
GCP_PROJECT_ID=my-google-project
GCP_SERVICE_ACCOUNT_EMAIL=my-service-account@project.iam.gserviceaccount.com
DATABASE_OWNER_PASSWORD=def
DATABASE_AUTHENTICATOR_PASSWORD=ghi

# there are some "scorched earth" drop statements you can uncomment for a full wipe
./act/cloud_sql_setup.sh
  # --hard for a full reset
  # --verbose to echo all commands

What don't I like about normal todo apps?

• I think tracking the amount of time something takes is valuable, and best done from a central system
• Task responsibility sharing is a very generally applicable concept
• Adding more structure to tasks or slowly and automatically (or through ui-dialectic) adding more context and "meaning" to tasks such as time horizons, etc seems valuable
• There are a lot of aspects of the task management domain that could be encoded in an app, but aren't, that I think could be valuable

feature ideas

• time tracking
• due dates
• duration, timers, alarms
• "staleness"? Some tasks get more important the longer they remain undone, some less
• task sharing
• tagging?
• gamification?