Features
What is in the beta, and what is coming
7 of 13 planned features are in the beta of the PrompTugal app 0.4.106. The team’s own app has more; those are listed in the developer area. The status of each one is not typed by hand: the site checks that the files that implement it exist in the source when the site is built.
All features
The PrompTugal app
| Feature | Built as | Status | Files that prove it |
|---|---|---|---|
| PrompTugal.news in the app | Web | In the beta | **/WebsiteView.swift |
| Offline reader | Native | In the beta | **/ReaderStore.swift, **/Content.swift |
| One schedule | Native and web | In the beta | **/ScheduleStore.swift, screen:team.schedule |
| Website and app talk to each other | Native and web | In the beta | **/AppBridge.swift, text:**/PublicShell.swift::.publicFeatures( |
| Reminders before sessions | Native | In the beta | **/ReminderScheduler.swift, text:**/PublicShell.swift::.publicFeatures( |
| The news, native and web side by side | Native and web | In the beta | screen:news.home |
| Your encrypted vault on the phone | Native | Coming | Packages/SGitVault/Package.swift, Packages/SGitVault/Sources/**/*.swift, screen:vault |
| Face ID or passcode unlock | Native | Coming | **/VaultKeychain.swift, screen:vault, text:**/VaultKeychain.swift::for protection in [Protection.faceID, .userPresence] |
| Trusted signers and your own vault | Native | Coming | text:**/VaultViews.swift::Trust this signer, text:**/VaultViews.swift::Make this my vault |
| The graph, drawn natively | Native | Coming | screen:news.graph |
| Ask, with your own key | Native | Coming | **/OpenRouterClient.swift, screen:collab.ai |
| Ask asks first | Native | Coming | text:**/AskView.swift::AskConsentSheet |
| Private in the app switcher | Native | In the beta | text:**/*.swift::struct PrivacyCover |
A feature is “in the beta” when every file pattern in the last column matches a file the PrompTugal app is built from: its own folder or a package it uses. The list lives in website/features.json.
Native, web or both
How we decide where a feature lives
We ask four questions, in order, and the first “yes” decides.
- Does it need the device? Face ID, the Keychain, notifications, widgets, the camera, background refresh. Then it is native.
- Does it hold a secret or private data that must survive? Then the key is native and the data goes in the vault.
- Is it content, or a workflow that changes every week? Articles, agenda pages, search. Then it is web, shown inside the app.
- Do people do it while walking between halls? Checking what is next, saving a session. Then it is a native fast path over the website’s data.
Some features are built both ways on purpose, side by side, so we can see which works better on a phone and on an iPad.
Requirements
What it runs on
- 18.0
- minimum iOS and iPadOS
- 0.4.106
- app version (build 1)
- 340
- Swift files
- 66
- Swift test files