A: Hey Sammy ! Great questions 👋

a) Today Digia is focused on powering native mobile app experiences (Android/iOS) through a server-driven architecture, the current platform is optimized primarily for mobile apps only.

b) Digia itself is framework-agnostic on the backend orchestration side, but the frontend SDKs currently support Flutter and native mobile ecosystems. React/React Native support is something we’re actively exploring based on demand, in terms of studio tech stack we are flutter heavy.

c) Yes - you can connect Digia with platforms like Supabase/Firebase etc which provide Apis very easily. Digia Studio includes an API Client that lets you connect to any REST or GraphQL APIs, so it works well alongside your existing backend stack rather than replacing it.

d) Digia is not primarily an AI-token consumption platform, so there are no mandatory AI token charges involved in core usage.

We have introduced an AI Builder inside the paid plans with fair usage limits included to make onboarding, prototyping, and adoption easier for teams. As AI workflows evolve, we’re also moving toward a BYOK-style model where teams can connect their own providers/keys depending on the use case.