Development Roadmap
Building in public. Here's what we're working on and what's coming next.
Dates are tentative and may shift based on testing and platform constraints.
Milestone 0: Dev Plumbing
CompleteM0.1–M0.10: Project setup, build system, CI/CD, testing infrastructure
Key Outcomes:
- •Gradle setup with Kotlin DSL
- •GitHub Actions CI pipeline
- •Basic UI scaffolding
- •Logging and debugging tools
M0.11: VPN Feasibility Spike
Feb 2026Prove VPN service can be stable and handle edge cases
Key Outcomes:
- •Stable VPN lifecycle (start, stop, crash recovery)
- •Persistent notification for VPN active state
- •Network traffic counters (up/down bytes)
- •Conflict handling with other VPNs
- •Kill switch to prevent leaks if VPN crashes
- •User consent flow for VPN permission
Milestone 1: Storage + Incidents + Privacy Foundation
Mar 2026Build the data layer and privacy controls
Key Outcomes:
- •Encrypted SQLite database for local storage
- •Incident logging schema
- •Privacy Center UI (retention controls, purge)
- •Sanitized export functionality
- •Basic settings persistence
Milestone 2: Monitor Mode Sensors + Baseline v0
Apr–May 2026Start collecting metadata and learning baselines
Key Outcomes:
- •Network flow sensor (no VPN yet, passive monitoring)
- •Permission usage tracker
- •App install source detector
- •Background activity monitor
- •Baseline calculation v0 (rolling window stats)
- •Basic drift scoring
Milestone 3: Protect Mode (VPN Enforcement MVP)
Jun–Jul 2026Wire up VPN containment based on drift scores
Key Outcomes:
- •VPN routing engine integrated
- •Per-app allow/block rules
- •Incident notification on containment
- •Review UI for contained apps
- •Approve/block controls
Milestone 4: Baseline Scoring v1
Aug–Sep 2026Improve drift detection accuracy and reduce false positives
Key Outcomes:
- •Multi-dimensional scoring (network + permissions + behavior)
- •Context-aware weighting (time-of-day, user location)
- •Confidence intervals for anomalies
- •Version-aware baseline updates
- •User feedback loop for false positive tuning
Milestone 5: MVP Hardening + Store-Ready UX
Oct–Nov 2026Polish for public beta and Play Store submission
Key Outcomes:
- •Onboarding flow explaining modes
- •In-app tutorial and help docs
- •Performance optimization (battery, memory)
- •Crash reporting and analytics (opt-in)
- •Play Store listing and marketing assets
- •Beta testing program launch
Our Development Principles
How we prioritize and what guides our timeline.
Privacy Over Speed
We won't rush features if it means compromising privacy guarantees. Each milestone includes privacy review checkpoints.
Stability Over Features
A buggy VPN that crashes is worse than no VPN. We prioritize rock-solid core functionality before adding bells and whistles.
Transparency About Limitations
If Android doesn't allow something, we document it clearly rather than promising workarounds that don't exist.
User Feedback Drives Tuning
False positive rates can only be tuned with real-world data. Beta testers will heavily influence drift scoring algorithms.