From Islam to Christ v0.2.28 is now the latest public Windows and Android release of the private, Bible-centered application. The current assets are published in the v0.2.28 GitHub release, with the product-named Windows installer and Android APK shown on the portfolio.

This distinction matters. A build can compile, a package can exist, and a public release can still be unsafe or incomplete if signing, rights, or device evidence are missing. This update records each boundary plainly.

What v0.2.28 carries forward

The source continuation brings together the recent product work:

  • A first-launch decision screen with the requested solemn “YOU MADE THE RIGHT DECISION” message, John 14:6, and “ENTER THE LIGHT” action.
  • An immediate Privacy Protection choice with discreet startup behavior, an Android Quick close action, bounded local PIN failure throttling, Android backup exclusion, and an Offline-only network boundary.
  • Automatic in-app language translation with English as the main language, bundled-language fallback, translation status, local caching, and right-to-left layout for Arabic, Persian, and Urdu. Private notes, reflections, typed searches, and other user-entered content remain outside translation requests.
  • Facts & Info educational reading paths, Muslim-seeker questions, Bible navigation, study packs, testimonies, prayer, local read-aloud, and source-library routing that keeps the raw local research boundary visible.
  • GitHub-linked updater safety: Android downloads into private app storage and hands the package to Android’s installer only after the user chooses Install update; Windows remains inside the Electron updater path.
  • In-app About, Terms & Conditions, Rights & Usage, Credits, source notices, software credits, and external-service boundaries.

Two platform packages were built

The shared renderer and SQLite content boundary were rebuilt for both targets. Each data-index pass reported 1,566 local Data assets, 66 Bible books, 31,102 verses, 14,197 Strong’s entries, 3,369 Vine’s entries, and 12,234 original-language alignments.

The Windows x64 NSIS installer completed with Electron Builder 26.15.3 and Electron 44.3.0. The local file is named From-Islam-to-Christ-0.2.28-x64.exe, and the generated latest.yml identifies version 0.2.28 and the same product-named installer. The installer is not Authenticode-signed on this machine, so it is recorded as a local package rather than a signed public Windows release.

The Android release variant completed with version code 30, version name 0.2.28, package com.mcographics.fromdarknesstolight, application label From Islam to Christ, and compile/target SDK 36. It is a release-mode package, but it uses the existing Android debug signing key rather than a Google Play production key. It is published in the v0.2.28 release for users who understand that boundary; it may not update an existing installation signed with a different key, including a production-signed v0.2.27 package.

Verification remains part of the feature

The source passed the database, content review, Bible navigation, audio-state, accessibility, content-link, source-coverage, privacy, updater-safety, legal-information, license-audit, and artwork checks. The content review is still an audit, not permission: 1,553 assets need review and 13 carry source notices, with 0 of 1,566 cleared for redistribution. The public release workflow correctly refuses to turn that state into a public content release.

The local build also exposed the practical toolchain boundary. The machine’s default Java 26 runtime could not compile the project’s Java 21 source level, so the Android package was rebuilt with a portable Temurin 21 runtime kept outside the repository. That build succeeded without changing the project’s Android identity.

The public download is v0.2.28

The public v0.2.28 release is now the correct download entry. It contains the product-named Windows installer and Android APK, and the website points directly to both assets instead of the older app-debug.apk path. The Windows installer is unsigned, and the Android APK uses the existing Android debug signing key rather than a Google Play production key; users should review the release notes and install only when that boundary is understood.

The next release step is straightforward but important: complete the per-asset redistribution review, configure and protect one stable production signing key for this Android application, sign the Windows installer if public Windows trust is required, then run the tag-driven workflow and verify the public assets before calling a future release production-ready.