slow it · flow it · love it
flove is a bet on a slower internet — one where relating, not extracting, is the point. It's not one app but a small constellation of them, each exploring a facet of how we relate.
For a family of independent little apps to feel like one calm, trustworthy thing, they share a set of standards. These aren't bureaucracy — they're care made repeatable: the same gentle look, the same respect for your attention and your data, the same promises kept in every corner. This page gathers them in one place. They're living documents; they grow as flove does.
The stance underneath every design decision — the contract flove holds itself to.
Slow it · flow it · love it. flove is low-tech and relational on purpose. Calm motion, breathable layouts, generous whitespace. If a feature feels hypey or "AI-cool", it doesn't belong here. The point is never to dazzle — it's to be a quiet, dependable place to relate.
From that stance, a handful of firm commitments follow:
prefers-reduced-motion. Calm shouldn't mean careless.How a flove app is shaped — and the shared patterns that let dozens of them feel like one.
Every flove frontend is described by three orthogonal axes: how much it does, how it runs, and into which medium it reaches.
| Axis | Question | Values |
|---|---|---|
| tier | how many features? | nano · mini · basic · normal · advanced · super · mega |
| distro | which runtime / qualities? | CSS-pure → JS → backend |
| surface | into which medium? | hardware · 2D · 3D · AR · VR |
The same idea can therefore meet you at the size you want (a mini that does one thing, up to a rich advanced), in the form you need (dependency-free or fuller), on the surface you have. 2D is today's baseline. The full tiers matrix maps every app across its sizes.
The standards come in three files, by how firm they are:
Fifteen reusable patterns. Only onboarding is mandatory; the rest are adopted per app as it needs them.
tier-pop) to move between them.flove:lang.entry- · labeler- · wizard- · step-), so the same idea always carries the same name across every app.tier-pop unlock) as you engage.<App> · FLOVE — the app's favicon, its name, the family brand.flove:theme.flove-appy.js): a writer publishes a summary, the Appy readers pick it up — with a manual upload fallback for file://.The road from a constellation of local apps to a shared, community-curated web — without ever breaking local-first.
flove starts fully on your device. The plan turns that constellation into a backed-by-the-network experience while keeping the core promise intact: nothing leaves your device unless you publish it. The far horizon is a polysemic dictionary built bottom-up — every published thing becomes a multi-rated, multi-related object in a vocabulary the community curates together.
| Phase | What it adds |
|---|---|
| F0 · local | The mini tier of every app, persisted on-device and fully offline; your own summaries aggregated into a personal profile. |
| F1 · enriched | The basic tier plus a local AI companion (MyWizy) and occasional content download. |
| F2–F5 · nety | Identity, a shared common area, a global AI, and fuzzy aggregation across the community — served by the corporate backend. |
This is a roadmap, not a finished system. F0 ships today; the network phases are where flove is heading.
Standards don't stay on paper. A small toolkit keeps every app faithful to them.
flove is built in a human + AI pairing, and the recurring craft — tidying, checking, translating, publishing — is captured as reusable skills. They're how the standards on this page get applied and maintained, app by app.
Beyond its own file, each app carries two identity files that travel with it whenever
its mark changes — /rebrand (aka /update-image) creates or
updates them alongside the live surfaces. The
economy logo board is the
worked demo.
images/apps/logos/<app>/<app>-logos.htmlThe source-of-truth board for an app's mark: the chosen glyph, its size ramp (16·24·44·72) and its two animated takes, one mark per app in the app's own accent. Create it when an app gets a mark; update it when the mark is redrawn. A whole family may share one board — see images/apps/logos/economy/economy-logos.html.images/apps/captions/<app>.pngThe app's preview screenshot, shown on the category launcher and the demos-index preview. Add one when the app is created; refresh it when its look changes; keep it named by the app's current name (rename old files, e.g. crowdcrafting.png → crafty.png).Where a job is deterministic — packaging, publishing, generating derived files — it's a small script rather than a skill. These live in the repo and are run by hand when their inputs change.
flove.zip, the runnable local package the home page's "Download / Go local" button hands out.sw.js, the service worker that makes flove installable and offline-capable.404.html, the clean-URL "receptionist" that routes bare app names to their files.marc/blog repo, nested at flove/blog).apps/lowai out to LowAiorg/web → lowai.org, outside the main site.How this constellation actually got built — the record behind the standards.
The standards above are the what. The making-of is the how: a turn-by-turn account of the human + AI pairing that shaped flove, app by app. It's shown in full below, with two companion documents mapping the same story from other angles.
slow it · flow it · love it.