v0.2 bundles all four phases from the planning session into a single
shippable release. versionCode 2 -> 3, versionName 0.1.1 -> 0.2.
DOMAIN
- Add NoteColor enum (NONE / BLUE / GREEN / AMBER / RED / PURPLE).
- Note: isFavorite + color fields; checklistCounts / checklistSummary
helpers parsing '- [ ]' / '- [x]' lines.
- NoteRepository: new search(query) + setFavorite(id, value) methods.
DATA
- NoteEntity: additive @Index isFavorite + colorKey (Short).
- NoteRepositoryImpl: search uses ObjectBox 'contains' case-insensitive;
observeAll + search sort favourites-first then updatedAt DESC.
UI
- NoteListViewModel: debounced(150ms) query -> repository.search;
openSearch / closeSearch helpers; toggleFavorite.
- NoteListScreen: search bar in top app bar; star icon + 4dp colour
stripe per card; checklist summary line ('N open - M done').
- NoteEditorViewModel: toggleFavorite + setColor; initial-snapshot
fields captured on first non-null observeById for dirty detection.
- NoteEditorScreen: BackHandler + AlertDialog 'Discard changes?' on
unsaved edits; star toggle in top bar; LazyRow of colour swatches.
POLISH
- Discard-confirm dialog implements Development Plan §5.2.
- Real release signing config (signingConfigs.release pointing at the
dev keystore in keystore/); keystore/release.jks gitignored;
keystore/README.md documents generation & rotation.
- KMP migration deferred to v0.5 (tracked in plan §10).
COMMUNITY / GITEA
- .gitea/workflows/build.yml: assembleDebug on push & PR, APK as
artefact.
- CONTRIBUTING.md, CODE_OF_CONDUCT.md (Contributor Covenant v2.1),
.gitea/ISSUE_TEMPLATE/{bug_report,feature_request}.yml,
.gitea/PULL_REQUEST_TEMPLATE.md.
- README: v0.2 changelog + Gitea remote-setup instructions.
VERIFIED
- ./gradlew assembleDebug assembleRelease both green.
- Debug APK 25.6 MB, release 19.8 MB, both v0.2 / versionCode 3.
- apksigner verify: 'Verifies' / v2 scheme true.
- No INTERNET permission in either APK (privacy posture unchanged).
1.5 KiB
Release keystore
The actual .jks files in this directory are gitignored (see
/home/nick/.gitignore / .gitignore rules under "Release keystore").
This directory ships with no checked-in keys — every developer (and the CI runner) is expected to generate their own.
Generate a local dev keystore
This is the keystore the project's default signingConfigs.release points
at. Replace before publishing to any app store.
keytool -genkey -v \
-keystore release.jks \
-keyalg RSA -keysize 2048 -validity 10000 \
-alias incido \
-storepass incido_dev_keystore \
-keypass incido_dev_keystore \
-dname "CN=Incido Dev, OU=Local, O=Incido, L=Local, ST=Local, C=NZ"
The store password and key password are both
incido_dev_keystore — change them before publishing.
For Play Store / F-Droid distribution
Generate a separate production keystore and store the credentials
outside the repo (CI secrets, password manager, etc.). Replace the
signingConfigs.release block in app/build.gradle.kts with one that
reads from ~/.gradle/gradle.properties or environment variables so the
real passwords are never committed.
Do not lose your production keystore — without it you can never
publish updates under the same applicationId/packageName.
CI
Gitea Actions (/.gitea/workflows/build.yml) currently only builds the
debug APK, which uses the auto-generated Android debug keystore.
Add a release job once you have secrets for the production key.