Skip to content

About

The Nijatva website: 24 small, single-purpose Android apps with no Google Play Services, no accounts, no ads and no analytics.

Topics

Resources

Contributing

Stars

1 star

Watchers

1 watching

Forks

Repository files navigation

nijatva.github.io

Landing site for Nijatva, a suite of small Android apps built without Google Play Services, accounts, ads or analytics. Built in India.

Static HTML. No framework, no JavaScript, no external fonts, no analytics.

Current state

Item State
Site Live at https://nijatva.github.io/
Pages source main branch, / (root), legacy build, HTTPS enforced, custom 404 active
Repository nijatva/nijatva.github.io, public
nijatva organisation Created. All 22 repositories live under it
Custom domain Not active. CNAME.example is inert and nijatva.in is not registered
Repository "Website" field https://nijatva.github.io/, which resolves

Structure

index.html            landing page
apps.html             the 24-app directory, grouped by phase
developer.html        the developer profile page
apps/<slug>.html      24 app pages, one per app
architecture.html     layers, screen skeleton, roadmap, no-GMS rules
404.html              custom 404 (root-absolute links on purpose)
assets/tokens.css     generated: 3 schemes x 3 accents, contrast-checked
assets/site.css       component styles, all colours via tokens
assets/icons/*.svg    24 app icons, generated
assets/logo.svg       brand mark (saffron tile, indigo N)
assets/favicon.svg    browser tab icon (indigo tile)
og.png                1200x630 social card, generated
robots.txt, sitemap.xml, .nojekyll, CNAME.example
_build/               the generator: app data, icon builder, page builder

Appearance: theme and accent

The header carries an Appearance control with the same options as the app settings screen: System / Dark / Light / Black themes and Green / Saffron / Indigo accents.

  • Tokens live in assets/tokens.css, generated by _build/tokens.py. It builds the full 3x3 matrix, refuses to write if any text pair falls under 4.5:1, and is the only place colour values belong.
  • To add an accent, add it to ACCENT in _build/tokens.py, run python3 _build/tokens.py, then add a <label class="pill" data-swatch="..."> to APPEARANCE in _build/build.py and rebuild.
  • The choice is stored in localStorage under nj-theme and nj-accent. It never leaves the browser and there is no server-side state.
  • With scripting off, the site follows prefers-color-scheme and the default accent, exactly as before.

That is the only script on the site: inline, ~1.5 KB, no network calls. The footer says "no third-party requests" rather than "no scripts" for that reason.

App status

status in _build/apps_data.py is the only thing that drives every badge, card and roadmap row: shipped (a release you can download), in-progress (repository but no release) and planned.

It was set from the repositories on 17 November 2026: seven apps ship releases (Browser, Camera, Gallery, Music, Dialer, Contacts, Messages), Files has a repository without one, and sixteen are planned. Several of those releases are debug builds, and the app pages say so in the note field. Check the release list before changing a status; the site's credibility is the whole product.

The Appstore

apps/appstore.html is generated like every other app page, from an entry with suite=False in apps_data.py. It is not one of the 24, so it sits in its own Ecosystem section on the apps page and is excluded from the suite counts by SUITE = [a for a in APPS if a.get("suite", True)].

Its source is not published yet, so the entry sets source_public=False: the page shows no GitHub button and marks the repository as private. Remove that flag the day the repository goes public.

Developer page

developer.html follows the profile layout used by RepoStore: back link, circular avatar, name and handle, a stats card, location and contact rows, a GitHub button, and a row of what the developer maintains.

  • Photo. The avatar is a monogram by default. Drop a square image at assets/developer.jpg and run the builder — it switches to the photo with no markup change. The GitHub account has no real avatar uploaded, only the generated identicon, which is why the monogram is the default.
  • Numbers. Repositories, apps planned and "with code today" are set in build_developer() in _build/build.py. They were read from the GitHub API on 13 November 2026 and are not live. Refresh them when they matter, and keep the "figures read from GitHub" date on the page truthful.
  • The maintainers row lists the apps that have a repository today, with a +N tile for the planned ones. It replaces the "Contributors" row in the reference layout, because there are no contributors to list yet.

Editing

Do not hand-edit apps.html or apps/<slug>.html — they are generated.

  1. Edit _build/apps_data.py: app names, summaries, features, status, tile colour.
  2. Run python3 _build/build.py from the repository root.
  3. For a new icon, add a glyph to _build/gen_icons.py and run python3 _build/gen_icons.py.
  4. For the social card, edit _build/og.html and re-render it at 1200x630.

index.html, architecture.html and 404.html are written by the builder too, so text changes belong in _build/build.py. The CSS is plain and lives in assets/site.css.

Deploy

git add .
git commit -m "site: <what changed>"
git push

Pages rebuilds on every push to main; the site is live about a minute later.

Moving to the nijatva organisation

  1. Create the organisation nijatva at github.com/organizations/new (organisation creation cannot be done through the API).
  2. Transfer this repository to it and rename it nijatva.github.io. GitHub keeps the redirect, and the address becomes https://nijatva.github.io.
  3. The URLs already point at nijatva.github.io; if the domain changes again, replace them in _build/build.py, then rebuild. The canonical and og: URLs are absolute and break silently otherwise.

Custom domain (only after you own the domain)

Do not rename CNAME.example before the domain is registered — Pages will fail to verify and the site will show a 404.

When the domain lands, three things change together: the CNAME file, SITE in _build/apps_data.py (then rebuild), and the repository "Website" field.

Keeping the status honest

The site states what exists today, not what is planned. Two things go stale every time an app ships:

  • STATUS_LABEL / status per app in _build/apps_data.py — drives every card, badge and app page.
  • The roadmap table in _build/build.py (build_architecture) and the UPDATED date in _build/apps_data.py.

Change both in the same commit as the release, then rebuild. A landing page that claims a shipped app which does not exist is the one thing this project cannot afford.

Rules for this repository

  • No external fonts, scripts, analytics, cookies or CDNs. Icons, CSS and the social card are served from this repository.
  • The accent drives primary buttons, links, eyebrows, badges and the selected pill, so switching it visibly changes the page.
  • When assets/site.css or tokens.css changes, bump ASSET_V in _build/build.py and rebuild. The stylesheets are linked with ?v=N so a cached copy cannot keep showing the old colours.
  • One script, inline, for the theme choice only. The mobile menu and the Appearance panel are <details> elements, so navigation works with scripting off.
  • Every text colour pair is checked for WCAG AA contrast in all three schemes and all three accents by _build/tokens.py; the build fails otherwise.
  • One email address on the site: Vasudev.work@rediffmail.com.
  • Keep CNAME.example inert until the domain is real.

About

The Nijatva website: 24 small, single-purpose Android apps with no Google Play Services, no accounts, no ads and no analytics.

Topics

Resources

Contributing

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages