Turn Any Need Into a
Trusted Service.

FAQ MiniApp Studio

• What is KOBIL MiniApp Studio?

  KOBIL MiniApp Studio is the environment for creating, integrating, reviewing, and publishing services inside KOBIL-powered SuperApps. Teams can build a MiniApp themselves or use KOBIL MiniApp Creator to accelerate delivery.

• What is a MiniApp?

  A MiniApp is a focused application that runs inside a SuperApp and uses shared platform services. Users can access it without downloading and managing a separate standalone mobile app.

• Who can build a MiniApp?

  Enterprise development teams, agencies, partners, startups, public institutions, and approved third-party service providers can build MiniApps. Publication remains subject to the host ecosystem's technical, security, content, and governance requirements.

• Do we need a large mobile development team?

  Not necessarily. MiniApps can be built with familiar web technologies and delivered across iOS and Android through one service codebase. Complex business logic and back-end integrations may still require experienced developers.

• What is KOBIL MiniApp Creator?

  KOBIL MiniApp Creator provides a guided way to assemble the MiniApp experience and accelerate common implementation work. Teams can use it alongside custom development where specialized interfaces, logic, or integrations are required.

• Which KOBIL services can a MiniApp use?

  Depending on permissions, a MiniApp can use identity and access, payments, messaging, notifications, document signing, file management, analytics, and other platform services through KOBIL MCP and supported APIs.

• Can a MiniApp connect to our existing systems?

  Yes. A MiniApp can connect to enterprise back ends, cloud services, partner APIs, and systems of record. The SuperApp provides the user-facing and trust layer while business data and core processing can remain in existing systems.

• How is a MiniApp secured?

  MiniApps operate within the SuperApp's identity and governance model. Access tokens, permissions, API controls, review processes, and application-security measures help restrict each MiniApp to the users, data, and services it requires.

• Can a MiniApp use the user's SuperApp identity?

  Yes. Through OpenID Connect integration, an authorized MiniApp can use the authenticated SuperApp identity and provide Single Sign-On without asking the user to register or log in again unnecessarily.

• How is a MiniApp published?

  The MiniApp is configured, tested, documented, and submitted for the required security, compliance, and categorization review. Once approved, it can be published to the relevant SuperApp catalog and assigned to the intended audiences.

• Do MiniApp updates require a full app-store release?

  MiniApps and server-driven content can often be updated independently of the host app, reducing reliance on full mobile release cycles. Publication controls and applicable app-store or host-app policies still apply.

• Can we control which users see a MiniApp?

  Yes. Services can be assigned by audience, role, region, organization, subscription, or other permitted attributes. Anonymous and authenticated users can also receive different screens and service access.

• Can MiniApp performance and usage be measured?

  Analytics can be included to track adoption, usage, and service performance within the permitted data and consent model. The required events and reporting should be defined when the MiniApp is designed.

• How can we start building a MiniApp?

  Begin with one clearly bounded user need, the required back-end service, and the KOBIL capabilities it should reuse. KOBIL can then recommend the self-build, Creator-assisted, or jointly implemented path.