Version 2.0.6: Google Play submission
A new Version 2.0.6 build is being submitted to Google Play, with improvements to prompt handling, local 8B reasoning and Android 16 alignment.
These notes explain what changed and why each change matters. Some of the work is deeply technical, but the goal remains simple: keep the initial download manageable, keep private writing protected and make the app feel dependable in everyday use.
Week 1: Foundation and AI architecture
Preparing a large local AI model for delivery through Google Play.
Implemented the Manual Model Splitting Task, splitLargeModel.
Google Play has a 1.5GB limit per asset pack. The 3.1GB Gemma 4 model therefore needs to be divided into three roughly 1GB files—model_chunk_1, model_chunk_2 and model_chunk_3—so it can pass through the Play Store’s delivery system.
Integrated Play Asset Delivery with fast-follow logic.
This keeps the initial app download small at approximately 20MB. The larger AI components can then arrive automatically in the background immediately after installation.
Week 2: Security hardening
Building the app’s “Privacy Shield” around sensitive journal content.
Activated FLAG_SECURE at the Android Window level.
This prevents journal content from appearing in screenshots or screen recordings and automatically obscures the app in the Recent Apps switcher.
Hardened SQLCipher AES-256 encryption and the ProGuard release rules.
The database remains an encrypted “black box” if a device is stolen. Specific keep rules also prevent the release optimiser from removing or changing code required by the encryption layer.
Week 3: UX and AMOLED optimisation
Responding to tester feedback and improving clarity on high-contrast screens.
Overhauled onboarding PIN logic to support four to eight digits.
Testers found the previous five-digit requirement too restrictive. Moving validation into local state means the Continue button responds immediately and removes the previous lag.
Retuned the colour system for high-contrast AMOLED displays.
Default grey text was difficult to read on pure black screens. Headers now use bright teal, while body content uses white and gold to improve contrast on modern high-brightness displays.
Moved the beta-terms checkbox to the top of the onboarding screen.
Users were missing the agreement control when it appeared below the legal text. Its new position makes the required action clearer and has improved onboarding completion.
Week 4: Production readiness and Android 16
Finalising release compatibility, stable navigation and AI downloads.
Migrated the project to Target SDK 36 for Android 16.
This brings the release in line with Google Play’s 2026 requirements and the latest Android security and permission standards for API 36.
Implemented an overlay architecture for policies and guides.
Opening a policy previously restarted onboarding. Policies and guides now slide in as secure layers, preserving the information a user has already entered underneath.
Synchronised the AI Download Manager paths.
The downloader and AI engine now use the same /llm directory, resolving the issue that could leave the download indicator stuck at 0%.
Version 2.0.6: Google Play submission
LatestSynchronising AI prompts, extending local reasoning time and confirming Android 16 alignment.
Updated prompt synchronisation in the AI engine.
The engine now recognises prompts that are already formatted—such as the Archive Librarian’s scan—and does not add a second system message. This prevents the “double-system-message” bug and keeps the instruction passed to the model clean.
Extended the 8B model’s thinking timeout to 90 seconds.
The additional processing time supports deeper, more nuanced reflections without the response timing out prematurely on mid-range hardware.
Confirmed API 36 alignment for the Google Play submission.
Version 2.0.6 is aligned with the Android 16 requirements reported in the Play Console, keeping the submitted build current with Google Play’s platform expectations.
Current project status
Version 2.0.6 is being submitted to Google Play with the latest prompt, reasoning-time and API 36 updates added to the previous release-candidate work.
Stability
High. Previous unresolved-reference and unused-variable warnings have been cleared from the project.
Compliance
Configured for Google Play’s 2026 Target API 36 requirement and current Android permission standards.
AI readiness
The Archive Librarian is configured to reassemble the downloaded model chunks for a local, internet-free experience.
What this means for testers
The app should be smaller to install, clearer during onboarding and more dependable when downloading the local AI. Journal content receives stronger protection against casual screen capture, and policies can be checked without losing work already entered.
Release-candidate testing will still be used to find device-specific problems and confirm that these changes behave reliably outside the development environment.
Development details may change as testing continues. Between Paths Journal is a reflective wellbeing tool, not a medical device, diagnosis or replacement for therapy or professional care.
