lightning
From a working app to every phone in Egypt.
Three milestones, in order. Each lists what is done, what we are on now, and what comes next. Dates come when the work before them is finished, not before.
Finish the core. Open the workflow.
Two tracks at the same time: make the backend complete and the features whole, and set up how people outside the team can build with us. The detailed plan behind it has nine numbered milestones: a task titled [3C] is item C of milestone 3, and the codes on the items below point into it.
1a · backend and featuresthe app works, end to end
- [done]
The core, public since v1.5.0, now v2.1.2Ledger, budget, reports, investments, certificates and gold, cash planning, bank CSV import, Arabic. One ledger, every figure traceable. Windows ZIP and Android APK are on the Downloads page.
- [done]
Themes and a storePaid app themes, unlocked once per profile with a code; the store, rewards and leaderboard run on the site. They never change a number.
- [done]
Phone and PC, pairedEncrypted profiles on both, paired directly with no cloud. Bank SMS for CIB and NBE, review-only.
- [now]
Edit anywhere, one home confirmsEdit on the phone or the PC; the home device confirms each change. Pairing already finds nearby devices and checks a six-digit number.
- [done]
Investments, import and searchBrokerages across exchanges and currencies, cost per purchase with bonus shares and splits, PDF and Excel statements, currencies that match across banks, search that knows where you are, and shared prices published again. Done in the code, so their plans left the repository; the Release log says which release carries each.
- [now]
Ordinary-PC acceptanceRecovery and fault drills on an ordinary Windows PC, including the reboot drill and power-loss evidence.
- [now]
Legacy import and in-app restoreBring old data in, and restore a backup from inside the app, both proven end to end.
- [next]
A trusted price source for Europe and the GulfLicensed or live-verified prices for European and GCC shares. The adapters exist; the source does not yet.
- [next]
Honest asyncRoutes are async def with synchronous database work inside. Make them one or the other.
- [done]
Windows in-app updatesSettings checks for, downloads and installs a new version: it verifies the signature, swaps folders, keeps the old one for rollback and never touches profiles. v2.1.2 is the first updater release, installed by hand; later versions update from inside the app.
1b · open-source workflowanyone can help, safely
- [done]
Public source, plain termsEvery line on GitHub. Contribution terms in CONTRIBUTING.md: you keep your copyright.
- [done]
Rules a newcomer can followAGENTS.md, one plan in issues/ with a code for every item, and an architecture that tests enforce, not reviewers.
- [now]
A public roadmapThis page. Kept in step with NOW.md and the plan in issues/.
- [now]
Issue templatesBug or improvement, and Good first issue, are live. Bank SMS format next, with redacted samples only.
- [now]
Good first issuesSmall and self-contained, with the file to open named. Comment /take and a bot assigns it to you.
- [done]
CI on every pull requestTests, dependency review and CodeQL run on each PR; the template asks what changed and how you checked it.
- [done]
A security policySECURITY.md: report a flaw privately through GitHub, never in a public issue.
- [done]
Setup in one clickOpen in Codespaces: everything installs and the demo household opens in your browser.
- [done]
Clear review rulesCONTRIBUTING.md: who reviews, who merges, and what every change must pass.
- [now]
A home for contributorsEvery task, claim and question lives on its GitHub issue. A short monthly note on what landed next.
Publish on Google Play.
The Android app already runs from the same code. This milestone makes it a store app.
play storeandroid first, it's what most of Egypt carries
- [done]
An Android app from the same codePython runs on the phone through Chaquopy. A signed arm64 APK is out to testers.
- [now]
The SMS permission declarationGoogle Play asks why the app reads SMS. Ours: bank messages, suggested as transactions, always confirmed by you.
- [next]
A Play-ready buildAn Android App Bundle with Play App Signing, 16 KB page support, and the target API level Play requires.
- [next]
Data safety, told plainlyNo account, no cloud, data stays on the device. The form and the privacy policy say the same thing.
- [next]
A store listing in two languagesEnglish and Egyptian Arabic, with real screens from the sample year.
- [next]
A closed testTesters from the WhatsApp and Discord groups on Play's closed track before anything goes public.
- [later]
Public releaseThen updates arrive through Google Play, like any other app.
Publish on the App Store.
The hardest port: the Python core, encrypted, on iPhone. Nothing here has started, and we say so.
app storeiOS, after Play is out
- [later]
Python on iOSCPython supports iOS since 3.13. Build SQLCipher and cryptography for it, and never swap in plaintext SQLite to make it work.
- [later]
A native shell around the same screensThe same pages and the same rules, paired with the PC the same way.
- [later]
Face ID, optionalA third lock on the same key, like fingerprint on Android. Password and recovery key always still work.
- [later]
TestFlightAn Apple developer account and a TestFlight beta for testers.
- [later]
App Store reviewPrivacy labels and Apple's rules for finance apps, met before we submit.
- [later]
App Store releaseLightning on iPhone.
Pick something from M1.
Build it with us.
New here? Take a good first issue: comment /take and it's yours. For anything bigger marked [next], say which on an issue first, so two people don't build the same thing.