Tasky

Product

Screens

Set up a challenge, tick daily tasks, review history, share status, and back up your progress — all offline on the phone.

Close

Everyday use

Use cases

Built for people running a personal challenge, not for teams or coaches.

• Start a 75-day challenge

  Add daily rules as tasks, leave Total Days at 75, tap Start Challenge.

• Move mid-challenge from a notebook

  Set Start Day to where you already are so you don’t lose the streak.

• Continuous vs Extend

  Calendar days always advance, or only move forward when every task is ticked.

• Stay accountable

  Message or share “Day 12 ✅ / ❌” to the app you pick. Reminder notifications nudge you.

• Change phones without losing progress

  Export a backup JSON, then Import after reinstall.

• Night-friendly OLED

  True-black theme for late check-ins without glare.

Engineering

How it’s built

The Android source stays private. This public repo only holds the showcase, license, disclaimer, and signed APK releases.

1. Push to private main

   CI bumps the version, runs JVM unit tests, and builds a release APK signed with the upload keystore from GitHub secrets (not a throwaway debug key).

2. Publish only if tests and build succeed

   Pull requests stop after test/build. On main, a fine-grained PUBLIC_REPO_TOKEN (Contents: read/write on this repo only) checks out tasky-app, syncs the private repo’s public/ folder with rsync, and pushes.

3. GitHub Release + APK

   CI creates tag vMAJOR.MINOR.PATCH.BUILD here, attaches Tasky-….apk and a .sha256 checksum, then commits the new version.properties back to the private repo.

Versions handle themselves

Releases use MAJOR.MINOR.PATCH.BUILD. Every publish increments the last digit unless you flip a bump flag before pushing.