Repository navigation
Releases
v0.4.0-beta.1
A patch release. We built a new app from scratch using only the public docs, and fixed what got in the way.
Android is supported; iOS is experimental and untested.
Fixed
- A new project's first Android build no longer fails.
valence codegennow adds core library desugaring toandroid/app/build.gradle.kts. Before this, the firstflutter build apkfailed with "Dependency ':flutter_local_notifications' requires core library desugaring", which names a plugin you never added. If you already added the two lines yourself, nothing changes. valence doctornow fails whenappIdand the AndroidapplicationIddiffer. It used to only warn.flutter createpicks anapplicationIdthat is usually not yourappId. When they differ, the forced-update screen andapp.openStoresend users to a Play listing that does not exist.- Doctor has a new Android desugaring row and accepts
linksas a native-value capability. An empty array in.valence/test-matrix.jsonis now a warning, not a failure. The warnings about missing doctor files now link to where those files are documented. - Doctor also checks that
pubspec.yamldeclares the bundle assets. Without them the build succeeds, and the app then starts with "no bundle to serve". The host's error for that case now points topubspec.yamlinstead ofrequires.bridge. - The wizard warns when a SvelteKit app has no static adapter (
sv createdefaults toadapter-auto). It now also says, before it asks for them, that the app id and both URLs are compiled into the app.
Docs
- The quick start now explains what the "project root" is and lists what to do before your first Android build.
- Seed data: a writable bucket cannot be seeded, so starter rows go in a read-only bucket.
- Deep links: Back from a view that a link opened on a cold start leaves the app. The page shows the pattern to use instead.
- The two
.valence/files that doctor reads are now documented. - Offline testing:
adb reversekeeps working in airplane mode, so remove it before you test offline. - Rollback: how to make a SvelteKit build reproducible, so a rollback downloads nothing new.
llms.txtnow starts with its page index.- Code samples import the bridge through
#lib, SvelteKit 3's alias. The quick start covers the bundle assets and padding for the system bars.
Upgrade
npx create-valence@latest update
flutter pub upgrade valence # in your host
npm i @getvalence/bridge@latest # in your web app
Then run node valence/valence.mjs doctor and fix any new FAIL rows.
Known limits
- iOS is experimental and untested.
- On Android, if the system kills the WebView's renderer, the app closes. Start rollouts at 10%.
- Remote push (
valence_push) has not been tested on a device yet.
Valence 0.4.0-beta.0
The first public beta. Android is supported; iOS is experimental and untested.
In short
Valence lets a web app become a mobile app's interface. A small Flutter host ships through the stores
once; after that, every UI release is a signed bundle that each phone downloads, verifies, tries and
rolls back on its own if it fails to start. Data lives in native SQLite, so the app works offline and
syncs incrementally when it can.
New in 0.4:
- Two packages instead of generated code. The host runtime is
valence
on pub.dev and the web client is@getvalence/bridge
on npm. Yourmain.dartis about twenty lines, and runtime fixes arrive as ordinary package updates. - Your own backend and login. The page hands the host a token; the host keeps it in the Android
Keystore, sends it on every sync, and will not mix one account's data with another's. - Native capabilities: deep links, local reminders, permissions, image sharing, connectivity and
lifecycle events, an offline REST cache, and a plugin directory. Remote push is opt-in through the
separatevalence_pushpackage, so Firebase is not in your app
unless you add it. - Safer releases: explicit update checks, a
ready()that cannot commit a bundle that never rendered,
rollback that says when it cannot serve its replacement, andvalence doctorfor diagnosing a project.
Start: npm create valence@latest in your web project, or read the
quick start.
Known limits, plainly:
- iOS is experimental and untested. The code paths exist; nobody has run them on Apple hardware.
- On Android, if the OS evicts the WebView's renderer under memory pressure, the app closes. Your data
is safe, but the event counts against a release's trial, so start rollouts at 10%. - Push is untested on a device until a Firebase project exists.
The full fix-by-fix notes are in CHANGELOG.md.