Tech stack
Built to last
Every Zovia app runs on the same stack. Here it is in layers, from the screen you touch to the tools we build with.
Versions and app lists on this page are read from our code each time the site is built. Last read November 13, 2026.
Layer 1
The app
One Flutter codebase per app builds for iPhone and Android. Under it sit 43 shared packages that every app draws on, for sign-in, payments, notifications, caching and more.

-
Flutter
3.44Written in Dart 3.12. One codebase per app builds for iPhone and Android.
-
Riverpod
3.4State management for screens that share state, in the apps that use it.
-
The Z design system
One set of components, type, color and spacing that every app is built from, so a new app starts with a finished look.
-
Phosphor icons
2.1One icon set across every app and this website, so no screen draws its own.
Layer 2
Data
Every app talks to one backend. Your phone keeps a copy for speed, and the server keeps the truth.
-
Parse Server on Back4App
An open-source backend that we host on Back4App. Apps reach it through our own cloud functions, and the server checks who is asking on every call.
-
Hive CE
2.19Cache-first reads. A screen draws from the copy on your phone first, then refreshes from the server.
-
Optimistic writes
Where a tap changes your data, the screen updates at once and the write goes to the server in the background. If it cannot be saved, the screen goes back and you are told.
-
Your account, on every phone
Your data belongs to your account on the server, so a second phone you sign in on shows the same data.
Layer 3
Identity
No passwords, and no email required. Your phone is the credential, and there are three ways back in if you change phones.

-
Device credentials
Signing up takes one tap. The app enrolls your phone and creates the account, with no email, no password and no code to type.
-
Recovery code
Shown once, when you start. It is the way back in if you lose your phone.
-
QR pairing
Add another phone by scanning a QR code on one that is already signed in.
-
Passkeys
A passkey on your phone is another way back in, with nothing to type.
-
Email is optional
You can add an email from your profile later. Nothing requires one.
-
Sensitive actions
Deleting your data asks for Face ID or your device passcode first.
Layer 4
Cloud and edge
The edge serves this website and carries small jobs. The apps report usage, crashes and push through the services below.

-
Cloudflare Pages
Serves this website. Pages Functions sit behind the contact form and the blog likes.
-
Cloudflare Workers and KV
Workers receive billing webhooks and pass them to our backend. Workers KV holds small counters, like blog likes and the contact form rate limit.
-
Firebase Analytics
Usage events, so we can see which features get used and which do not.
-
Firebase Crashlytics
Crash reports, so we can find and fix what breaks.
-
Firebase Messaging
Push notifications, such as reminders and household activity.
The Firebase plugins build on firebase_core 4.13.
Layer 5
Intelligence
AI calls run on the server, so AI keys stay off your phone. One small step runs on the device itself.
-
Photos read in the cloud
Photos you scan go to a cloud AI service for reading. The server makes the call, so no AI keys sit on your phone.
-
Places and travel time
Place details and travel time with traffic are looked up in the cloud.
Used in
-
Google Maps
The map itself, in apps that show a place on one.
Used in
-
ML Kit image labeling
Runs on the phone. Zarden uses it to check a photo before the photo is sent to identify a plant.
Used in
Layer 6
Payments and attribution
How money reaches us, and which apps measure where an install came from.
-
App Store and Google Play billing
Purchases and subscriptions go through the stores. Prices are read from each app's product catalog when this site is built, so a price on this site is the price in the app.
-
RevenueCat
10.9Sits between the stores and our backend. It checks purchases and tells our server when a subscription starts, renews or ends.
Analytics and attribution, stated plainly
Firebase, listed under Cloud and edge, collects usage events and crash reports.
These apps also ship an attribution SDK that measures which ad led to an install:
On iPhone, your advertising identifier is used only if you allow it when asked.
There are no ads inside our apps, and we do not sell your data. Each app's privacy policy lists what it sends and to whom.
How we build
The tools behind the code
30,000+ automated tests are written across the apps, the shared packages and the cloud code. They are counted from the source each time this site is built.

-
Claude Code
Our coding assistant. A change that touches money, sign-in, privacy, child safety, deletion or concurrency also gets a separate review from a reviewer that did not write it.
-
Figma
New components and brand marks are designed in Figma before they are built.
-
Fastlane
Builds and store uploads run through Fastlane lanes.
-
The Studio Baseline
Our shared engineering standards, such as lint rules, schema checks and the deploy gate. Every repo keeps its own copy and syncs it from one source.
-
Local gates
Checks run on our own machines before a push, before a store release and before a cloud deploy.
Credits & Acknowledgments
Credits
Standing on the Shoulders of Giants. The technologies and communities that make Zovia possible.
Development Platform
-
Flutter & Dart
We chose Flutter because maintaining separate iOS and Android codebases would mean half the polish and twice the bugs. Flutter lets us deliver native performance on both platforms without compromise. Every animation, every interaction, every pixel is crafted once and works beautifully everywhere. This isn't about cutting corners, it's about focusing energy where it matters: the user experience.
AI & Intelligence Partners
-
Anthropic (Claude Code)
Claude Code isn't just a tool, it's a development partner. Every package, every screen, every line of documentation was written in collaboration with Claude. It understands architecture, catches edge cases, and maintains consistency across every package. Zovia wouldn't exist without it.
-
OpenAI (ChatGPT)
ChatGPT is our thought partner for design decisions, architecture debates, and philosophical questions. When we're stuck on a UX problem or debating paradigms, ChatGPT helps us think through the trade-offs. It doesn't write code, it helps us think better.
-
Google Cloud Platform
We use 25+ Google Cloud APIs: Gemini AI for place intelligence, Voice for transcription, Vision for scanning, Maps for location services, and more. Google's AI infrastructure powers the smart features that make Zovia apps feel intelligent without being intrusive.
Backend & Infrastructure
-
Back4App
Back4App kept Parse Server alive when Facebook abandoned it in 2017. We chose them because they believe in open source and no vendor lock-in, if they ever disappear, we can self-host. That's the kind of partner we want. Plus, their infrastructure just works.
-
MongoDB
MongoDB's flexible document model matches how we think about data. No rigid schemas, no migrations every time we add a field. It lets us iterate fast without breaking production. Parse + MongoDB is the most developer-friendly backend stack we've found.
-
Firebase
Firebase handles analytics, cloud messaging, and storage. It's Google infrastructure that scales automatically. We don't think about servers or capacity, we just build features. That's exactly how backend services should work.
Communication
-
SendGrid
SendGrid delivers our OTP codes and notification emails. Email infrastructure is hard, deliverability, spam filters, reputation management. SendGrid handles all of it so we can focus on crafting the message, not fighting mail servers. And their emails actually arrive in inboxes, which is rarer than it should be.
Design & Creative
-
Phosphor Icons
Phosphor Icons understand what we understand: consistency is invisible, but its absence is jarring. Their 1,512 icons gave us a complete visual language we never had to compromise. Six weights, perfect geometry, open source. We use them exclusively across every screen, every app, every interaction in the Zovia ecosystem.
-
Figma
Figma is where ideas become interfaces. Component systems, design tokens, prototypes, all in one place. It bridges the gap between concept and code. And because it's browser-based, we can design anywhere. Figma didn't just replace Sketch, it reimagined what design tools should be.
-
Unsplash
Unsplash gave the world a gift: millions of high-quality photos, free to use, no strings attached. Photographers share their work generously, and we benefit from their craft. The images you see across Zovia's website and marketing come from Unsplash's incredible community.
-
Midjourney
Midjourney turns words into visual concepts. When we need imagery that doesn't exist yet, abstract ideas, impossible perspectives, dreamlike aesthetics, Midjourney helps us visualize it. It's not replacing artists; it's expanding what's possible for small teams with big ideas.
Distribution
-
Apple App Store
Apple's ecosystem sets the standard for quality. Their review process is rigorous, their APIs are thoughtfully designed, and their platforms push us to build better apps. Sign in with Apple, StoreKit, CloudKit, every API feels crafted with care.
-
Google Play
Google Play brings Zovia to billions of Android devices worldwide. Their Play Billing system handles payments seamlessly, and their distribution infrastructure ensures users can download our apps instantly, anywhere. Android's openness complements iOS's polish.
Development Tools
-
GitHub
GitHub is where code lives and evolves. Version control, collaboration, code review, it's the single source of truth for every line of Zovia. GitHub didn't invent git, but they made it accessible. That's a gift to every developer.
-
Cloudflare Pages
Cloudflare Pages serves the site from a global edge network. Wrangler deploys, instant rollbacks, automatic HTTPS, the same network powering our deep links and Workers. Hosting that gets out of the way so we can focus on building.
Build your own
This stack is yours to build on
Zovia Snapshot ships the same production Flutter and Parse foundation you just read about, plus a Claude Code guide that walks you from setup to a shipped app. Own it, build with it, ship your own.