How Flowo Handles a Deletion Request, Step by Step
A deletion request in Flowo runs as a server scrub and a local erasure that report separately. This article walks through the order, the key and the export.
Topic
16 articles on Engineering.
A deletion request in Flowo runs as a server scrub and a local erasure that report separately. This article walks through the order, the key and the export.
How BBMM Technologies handles secrets for Flowo: a gitignored dev file, build-time defines, a validator that fails a release, and a scan of every commit.
How Flowo's planner handles time: an injected clock, calendar days built by constructor, day counts at UTC midnight, and tests in named zones on DST nights.
How Flowo schedules iOS local notifications: one-shot triggers at absolute instants, a budget under the pending limit, stable ids and a path that never prompts.
How to learn enough from crashes to fix them while collecting no more user data than necessary, keeping diagnostics and privacy compatible.
Releasing too often wears a team down, and releasing too rarely lets risk pile up. A steady, predictable cadence keeps quality high at a pace people can sustain.
People are interrupted mid-task constantly. Preserving state, marking where they left off, and restoring context turn a jarring return into a smooth resumption.
How the Flowo backend limits AI requests without user accounts: attested devices, per-device rate limits, atomic daily quotas and gates that fail open.
Choosing well-understood, proven tools over novel ones is an underrated engineering strategy. Why boring technology often delivers more than exciting alternatives.
How Flowo changes its on-device Hive schema without losing data, using stub adapters for retired types and a backup before every destructive rewrite.
A small app needs enough logging to answer what happened, without drowning in noise or capturing personal data.
A practical threat modeling method that a small team can run in an afternoon to find and rank security risks before they ship.
How to keep a native macOS app fast by protecting the main thread, measuring with the right tools, and working to explicit performance budgets.
A component library succeeds when it reduces the decisions developers make. Composition, tokens, and clear ownership keep it usable as it grows.
Real connectivity is intermittent. How to build apps that stay usable on slow links and degrade gracefully when the network disappears entirely.
Reliable undo lets people act without fear. How to design forgiveness through reversible actions, clear scope, and recovery rather than confirmation dialogs.