0005 - Continue Building on Apollo/Uncrew UI with Feature Flags
| Classification | CONFIDENTIAL |
| Organization | DroneUp |
| Date | April 2026 |
| Status | Pending |
Decision
The Talos demo frontend will be built on the existing Apollo/Uncrew UI, not a new standalone frontend. Uncrew-specific tabs and features will be hidden via feature flags (env-driven sidebar visibility) for demo presentations.
Context
| Option | Pros | Cons |
|---|---|---|
| New standalone frontend | Clean slate, no Uncrew baggage | Significant effort to rebuild map, auth, layout; duplicates work |
| Apollo/Uncrew UI + feature flags | Oleksii already built pilot submission flow; map integration exists; team is fluent | Couples to Uncrew codebase; need to manage visibility flags |
| Szymon’s prototype UI | Good for backend validation | Not production-quality; was only a PoC for jurisdiction API |
The team chose Apollo UI because:
- Oleksii has already built the pilot submission, profile, and authorization review flows
- Map integration (Mapbox), traffic visualization, and API proxy config already work
- Feature flags (env-driven sidebar config) can hide Uncrew tabs for Talos demos
- A new domain can be provisioned to serve the same frontend without Uncrew branding
Consequences
- All frontend Talos work happens in
uncrew-apollo-frontendrepo - New Talos views added as new routes/tabs
- Env variable controls which sidebar items are visible
- If Talos becomes a separate product, frontend can be forked or extracted
Last updated on