Architecture

Four modules, 24 apps, one rule.

Local-first, zero-tracking, no Google Play Services. This page is how the suite is actually put together, including where the build stands today.

1 · Layers

The foundation sits on nothing

Everything in the suite sits on these four repositories, and the apps sit on top of them.

F4 · nijatva-suite App index, release downloads, self-hosted F-Droid style repository
F1 · nijatva-coreCompose UI, SAF, backupDesign system and shared helpers
F2 · no-gms-checkGradle plugin, CI actionFails the build on any GMS artefact
F3 · nijatva-designIcons, templatesKeeps 24 repos looking like one suite
Phase 1 · 5Calc, Clock, Notes, QR, Files
Phase 2 and 3 · 15Gallery, Music, Recorder, PDF, Device Info, Weather, Dialer, Contacts, SMS, Calendar, Camera, Expenses, Tasks, RSS, Vault
Phase 4 · 4Keyboard, Launcher, Browser, App Manager

F1, F2 and F3 are not decoration. If nijatva-core lands late, twenty apps grow twenty copies of the same Storage Access Framework helper. If no-gms-check lands late, the no-GMS claim stops being a build failure and becomes a promise.

2 · One skeleton

Learn one app, know all 24

Every app uses the same Compose skeleton, so a user who learns one app knows all twenty-four.

← Nijatva NotesOffline mode
SAF folder access: grantedINTERNET: not requested
the primary surface
Markdown editor, media grid, dialpad, reader
Home
Vault / Local
Settings

Two rules are visible in the skeleton itself

The privacy state is on the screen, not buried in settings. A banner states whether storage access is granted and whether the app holds INTERNET. For the keyboard and the calculator the honest answer is "not requested", and saying it out loud is the product.

The middle bar reads Vault / Local, never Cloud. There is no sync target to put there.

3 · Roadmap

Roadmap and real status

28 repositories planned: 4 foundation repos and 24 apps. All four foundation repos exist, eight apps ship releases and one more has a repository. Status as of 13 November 2026.

Repository counts are planned totals, not a count of what exists today.
PhaseScopeReposAppsTargetStatus
Phase 0Foundation base4 nijatva-core, no-gms-check, nijatva-design, nijatva-suite2-3 weeks 4 repos, core has code
Phase 1Small apps5 Calc, Clock, Notes, QR Scanner, Files4-6 weeks Files and Notes repos created
Phase 2Media and utility6 Gallery, Music, Recorder, PDF Viewer, Device Info, Weather6-8 weeks Gallery and Music released
Phase 3Phone roles9 Dialer, Contacts, SMS, Calendar, Camera, Expenses, Tasks, RSS, Vault8-10 weeks 4 of 9 released
Phase 4Flagship4 Keyboard, Launcher, Browser, App Manager10-12 weeks Browser released

7 apps are easy, 12 medium and 5 hard. The timeline assumes part-time work and is a floor, not a promise. Seven apps have public releases (Browser, Camera, Gallery, Music, Dialer, Contacts, Messages); Files and Notes have repositories without one. Several of those releases are debug builds, which the app pages say plainly.

Outside the 24

Seven projects sit beside the plan and are not counted in the table. Each has its own page on the apps screen: the Appstore, Photos, Video Player, Drive, Browser Mini X, Photo Editor and the Web Store. Two of them are not one app but a family: the video player ships for Android, Windows, macOS, Linux and the web from one Compose Multiplatform codebase, and nijatva-video-player is its Android-only sibling.

4 · No-GMS

BharOS and no-GMS compliance

What is banned, what replaces it, and why.

ComponentNeverNijatva replacementNote
Push notificationsFirebase Cloud MessagingUnifiedPush / ntfy / foreground WebSocketMost apps here need no push at all
Storage accessMANAGE_EXTERNAL_STORAGEStorage Access Framework, Photo PickerA revoked grant shows an empty state, not a crash
Maps and locationGoogle Maps SDK, FusedLocationProviderosmdroid / MapLibre + OSM, LocationManagerManual city entry is the primary path
On-device MLML Kit (Play Services variant)Bundled TFLite / whisper.cpp / VoskModel ships in the APK, runs locally
AdsAdMobNothingAn ad SDK is a tracking SDK
Crash and analyticsCrashlytics, Firebase AnalyticsNothing, or self-hosted Sentry; local log exportDefault is nothing
AccountsGoogle Sign-InNo account at allThis is the entire pitch
App updatesPlay Core in-app updatesOwn F-Droid style index on Pagesnijatva-suite does this
DistributionPlay StoreAPK repository, Nijatva Appstore, F-Droid, sideloadSigning key never in the repo

5 · Corrections

Two mistakes, recorded

Kept on the page so the same two do not come back.

nijatva-core does not sync anything

The first draft described core as "Compose UI + SAF + Sync". There is no sync in a local-first suite. Core carries the design system, SAF helpers, a text-to-speech wrapper, encrypted preferences and local backup and restore.

AdMob is advertising, not analytics

The draft grouped "AdMob / Crashlytics" under one heading. They are two separate bans: no ad SDK, and no analytics SDK. The second is the one people forget, because a crash reporter usually ships telemetry along with it.

Repository naming

nijatva-<app>, lowercase and hyphenated. Foundation repos follow the same rule.

Package name

in.nijatva.<app>, fallback com.nijatva.<app>. Locked before the first release.

Display name

Nijatva <App>, one prefix everywhere, never abbreviated.