FAQs
Frequently Asked Questions
What is Digia?
Digia is a frontend orchestration platform for mobile apps. It enables teams to create, manage, and release UI and logic from a centralized dashboard—without needing to rebuild or redeploy the app through app stores.
How is Digia different from React Native or Flutter?
Digia is not a UI framework like React Native or Flutter. Instead, it sits on top of native or cross-platform apps (like Flutter) and powers them using Server-Driven UI (SDUI).
With Digia, teams define screens, flows, and logic on a backend dashboard, which are rendered instantly on the app.
Can Digia work with our existing React Native, Native, or Flutter app?
Yes. Digia supports brownfield integration—you can embed Digia-powered flows alongside existing native or Flutter screens.
React Native support is currently not available but is on the roadmap.
How does Digia impact performance?
Digia is built for high-performance mobile experiences. It uses lazy loading, optimized rendering engines, and micro-optimizations to consistently deliver 60FPS performance, even on low-end devices.
Does Digia support offline use cases?
Digia is optimized for internet-driven apps, where screens and data are fetched dynamically. While it does not support fully offline-first apps, it enables:
Input-based screens to work offline (if data is passed in locally)
Offline-first screen caching, allowing users to interact with previously loaded screens
Proactive caching of selected flows
However, we recommend against building completely offline-first apps with Digia.
How do I create and update screens using Digia?
Digia provides a visual builder where designers and developers can:
Compose UI using prebuilt or custom components
Configure business logic and API integrations
Preview updates in real-time
Version and release changes instantly
What happens if Digia’s backend goes down?
Digia includes local caching and default screen configurations within the SDK. If the backend becomes unavailable:
The app continues to function using cached data
Users experience no visible downtime
New updates won’t be delivered until backend service is restored
How does Digia handle analytics and events?
Digia integrates with tools like:
Mixpanel
Clevertap
Firebase
LaunchDarkly
It also supports:
Custom event tagging
Funnel tracking
UI event configuration directly from the dashboard
Clickstream callbacks for integration with any external analytics system
All analytics are version-controlled and managed server-side.
What’s the developer experience like?
Developers benefit from:
Sandbox preview and testing environments
Version-controlled screen definitions
Real-device testing via SDK or companion app
Autocomplete and two-way data mapping
Runtime safeguards and compile-time validation
Robust debugging tools and expression engine
This ensures fast development cycles and fewer runtime issues.
Can Digia support high-concurrency events like flash sales?
Yes. Digia is designed for scale. It has successfully handled flows with over 10 million concurrent users, including performance-intensive and time-sensitive workloads.
How do releases work in Digia?
With Digia, releasing updates involves:
Designing or modifying screens, components, and logic
Promoting changes to a staging environment for testing
Releasing to production through a staggered rollout
All updates are delivered via Server-Driven UI—no app store resubmissions required.
Can we customize Digia’s component library?
Yes. Digia supports:
Custom components and reusable blocks
Design tokens and theming
Atomic components to build scalable design systems
Native component injection via the SDK’s component registry
This allows full alignment with your brand and extensibility for advanced use cases.
What platforms does Digia support?
Currently supported: Flutter, Native Android, and iOS
Last updated