Introduction

What kind of apps you can build?

Overview

Emergent is a general-purpose platform for building production-ready applications. Whether you're prototyping an idea, shipping an internal dashboard, or publishing a customer-facing SaaS product, Emergent's agentic workflow handles the full stack - frontend, backend, database, hosting, and published app.

You describe what you want in chat. The platform's AI agents write the code, test it, and publish it live. No frameworks to learn, no infrastructure to configure.

Not just prototypes

Emergent apps are real, production-grade projects. You get a live URL, custom domains, database persistence, and the ability to iterate continuously as your needs evolve.


For Individuals

Perfect for personal projects, creative experiments, and side hustles.

Common use cases:

  • Portfolios & personal websites - showcase your work with a custom design and domain
  • Habit trackers & productivity tools - build exactly the tracker you need, tailored to your workflow
  • Learning projects - test ideas, experiment with features, iterate without setup overhead
  • Content hubs - blogs, newsletters, link-in-bio pages
  • Micro-SaaS MVPs - validate a product idea before committing to a full build

All apps come with built-in hosting and a live URL. Add a custom domain to make it truly yours.


For Small & Medium Businesses

Emergent helps teams ship tools faster - without hiring a dev team or waiting months for an agency.

Common use cases:

  • Internal dashboards - visualize KPIs, track operations, manage workflows
  • Customer portals - let clients view orders, book appointments, submit requests
  • CRM & lead management - custom tools that fit your sales process
  • E-commerce storefronts - product catalogs, checkout flows, order tracking
  • Event & booking platforms - handle registrations, payments, scheduling
  • Marketing landing pages - quickly spin up campaign-specific pages with forms and analytics

Info

Teams often start with a simple MVP in Emergent, then expand it iteratively as they learn what works. The same app can evolve from a prototype to a production workhorse without platform migration.

Integration with third-party services (Stripe, Twilio, analytics providers) is straightforward - just describe the integration you need. See Custom & MCP integrations for details.


For Enterprises

Emergent supports complex, multi-user applications with authentication, role-based access, and scalable architecture.

Common use cases:

  • Enterprise dashboards & reporting tools - aggregate data from multiple sources, support large user bases
  • Workflow automation platforms - custom approval chains, ticket systems, process management
  • Customer-facing SaaS products - multi-tenant apps with user accounts, billing, analytics
  • Data collection & admin panels - manage large datasets, moderate content, enforce compliance
  • White-label platforms - publish customized instances for different clients or regions

Persistent database

Every app includes a MongoDB instance for structured data persistence. See Database (MongoDB).

Custom agents

Extend the platform's capabilities with domain-specific logic. See Custom agents.

Performance at scale

If your app handles high traffic or compute-intensive tasks, monitor performance early. See App slow, crashing or cold-starting for optimization guidance.


Mobile & Cross-Platform

Emergent builds both web and mobile apps. Conversion between the two works in one direction only: Web to mobile: available as a fork. The fork creates a new mobile job with the same backend. You will have the option to choose the nature of the forked job - to keep it as a web app or switch to a mobile app. The original web job keeps its own type and stays unchanged. Mobile to web: not supported. Start a new web job and rebuild it, using the mobile app as a reference. A job's app type never changes in place — conversion always creates a separate job, never an in-place switch.

  • Native mobile apps - iOS and Android from a single codebase

  • Responsive web apps - optimized for desktop, tablet, and mobile browsers

  • Progressive Web Apps (PWAs) - installable, offline-capable web experiences

Tip

Describe "make this mobile-friendly" in chat to adjust the UI and interactions. To convert a web app to a native mobile app, use the preview toggle or Publish panel "Add Mobile App" option, this forks your project into a new mobile job sharing the same backend. Note that mobile-to-web conversion is not available. Learn more: Web to Mobile conversion.


What's Next

1

Explore the workspace

Get familiar with the chat interface, preview pane, and published app controls. See A tour of the workspace.

2

Start building

Describe your first app in chat. Be as detailed or high-level as you like - agents will ask clarifying questions.

3

Publish & iterate

Once you're happy with the preview, publish live. You can continue refining in chat even after launch.

Info

Not sure where to start? Browse the Glossary of Emergent terms to understand key concepts, or jump straight into chat and describe what you want to build.


What each app type can use: database & APIs

Different app types get different backend capabilities:

App typeBuilt-in MongoDBExternal API access
Full Stack AppYes - built-in MongoDB (or connect an external database)Yes - call any third-party API from the backend
Mobile App (Expo/React Native)Yes - built-in MongoDB via its server-side backend (shared across platforms; separate preview & production databases), plus offline-first local storage on-deviceYes - external API calls go through that same backend
Landing PageYes - built-in MongoDBYes - call any third-party API

Note

Full Stack Apps and Landing Pages publish to a web URL; Mobile Apps build with Expo/React Native and ship through the app stores. A Full Stack App can be converted to a Mobile App (one-way) so both share the same backend. Mobile database/API behaviour: see Database & data on mobile.

Was this page helpful?

Related pages