Tech Stack
Every technical decision at Zovia is made with one question: "Will this serve users well in 10 years?"
Most apps are built to ship fast. Zovia is built to last. Every technical choice, from the modular package system to the offline-first architecture, reflects our values: clarity, craft, and respect for users.
This isn't about using trendy frameworks or chasing hype. It's about choosing proven, stable technology and architecting it thoughtfully for the decade ahead.
Why 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.
Most solo developers build everything in one place. We took a different path: 36 focused, reusable packages instead of a single monolithic codebase.
Authentication, Offline Sync, Design System, each package does one thing exceptionally well. Apps compose exactly the capabilities they need.
This means faster development, fewer bugs, and the ability to build new apps in weeks instead of months.
Your life doesn't pause when WiFi drops. Neither should your apps.
Every Zovia app works fully offline. Track counters, schedule activities, manage inventory, all without an internet connection. When you reconnect, everything syncs seamlessly in the background.
This required building sophisticated conflict resolution, queue management, and retry logic. But it means Zovia apps are reliable, always.
The apps we publish ourselves don't support tablets or iPads. Not because we can't, but because we choose not to.
Supporting every screen size dilutes focus. By optimizing exclusively for phones (the device you always have), we create experiences that feel native, fast, and perfectly sized.
This is craft over scale. Quality over quantity. Depth over breadth.
That is the rule for our own apps. For client work we build to the brief, including responsive web. For Finly we shipped a Flutter app and a companion website together.
We use Parse Server hosted on Back4App, an open-source backend that's been battle-tested since 2013.
Why not build our own? Because reinventing authentication, database management, and cloud functions would be ego, not craft. Parse gives us enterprise-grade infrastructure so we can focus on the app experience.
Plus, it's open source. If Back4App ever disappears, we can self-host. No vendor lock-in. No data hostage situations.
The Zovia Studio Design System is our atomic design foundation powering all Zovia apps. Think of it as our visual language: typography, colors, components, layouts, all defined once, used everywhere.
But here's what makes it special: it supports dual UI paradigms. Traditional layouts for productivity apps (Zupply, Zyve, Zistil, Zots, plus Zynq, Zarden, and ComingUp in development) and spatial, Monument Valley-inspired interfaces for games (Zuzzle).
Same design tokens, same components, different expressions. This is what lets us build diverse apps that still feel unmistakably Zovia.
Every screen in every Zovia app uses the same chrome stack via ZAppScaffold: floating glass top island, floating glass bottom nav, per-app accent gradient atmosphere, and a top fade that lets content dissolve under the bar. No per-app deviations, no per-screen workarounds.
We don't use Google Analytics, Facebook Pixel, or any third-party tracking. Your usage data stays between you and Zovia, period.
We do collect anonymized analytics through our own backend (using Parse Cloud Functions) to understand how features are used. But this data never leaves our control and is never sold.
Privacy isn't a feature we bolt on later. It's baked into the architecture from day one.
Every tool, service, and package powering the Zovia ecosystem.
Fast, efficient AI model powering natural language understanding, context-aware recommendations, and place intelligence.
Real-time weather data and 10-day forecasts with 30+ metrics, plus US EPA Air Quality Index for health-conscious planning.
OCR for receipt scanning and document text extraction in Zistil inventory app.
AI partners accelerate development while maintaining quality and thoughtful design.
Sign in once and access all Zovia apps. Our unified authentication system shares sessions securely across the entire ecosystem using zovia_session package with native IPC (iOS Keychain Groups + Darwin notifications, Android ContentProvider + BroadcastReceiver) for real-time cross-app sync.
Sign-up is a single tap. No email, no OTP, no password. Every user is a real account from minute one, with a per-device credential stored in the keychain.
Passkeys shipped 2026-05-08. RP ID zovia.studio with AASA and assetlinks.json served at zovia.studio/.well-known/. A single passkey covers every entitled Zovia app. Biometric is also used as a per-call sensitive-ops gate (regenerate recovery code, sign out other devices, delete account) via requireRecentAuth.
Crash and usage analytics via Firebase. Install attribution via Facebook SDK (install events only, no behavior tracking, no ads). Game telemetry through a custom Parse-backed pipeline.
The marketing site, the deep link redirector, internal prototypes, the email pipeline for Zyve, and the blog reaction system all run on Cloudflare's edge. One vendor, one dashboard, edge-deployed everywhere.
Pages projects
Workers + Pages Functions
Cloudflare KV
DNS, Domain, and well-known
Deploy tool
Every architectural decision, from modular packages to offline-first design, exists to serve one goal: creating apps that respect your time and earn your trust.