Unify Applications
Logo
Code-First App Creation

Code-First App Creation

Logo

9 mins READ

What Is Code-First App Creation?

UnifyApps offers two build modes when creating an application through the AI creation screen:

ai-create-screen.png
ai-create-screen.png

  • Code mode — uses the code builder. You describe what you want in natural language, the AI writes a real code-based application, and you continue refining it through a conversational chat interface. This is the code-first approach.

  • Config mode — uses the no-code page builder where you configure UI, data bindings, and logic visually without writing code. This is the config-first approach (covered in Config-First App Creation).

Code-first is aimed at developers and power users who prefer to express application logic in code, or who want to prototype quickly using an AI that understands software architecture. The resulting app is a genuine code application — not a configuration file — and the code builder remains the primary interface for ongoing development.

When to Choose Code-First vs. Config-First

ConsiderationCode-FirstConfig-First
Primary audienceDevelopers, technical usersBusiness builders, citizen developers
How the app is editedChat with the AI code builder; modify generated code directlyDrag-and-drop canvas; visual property panels
Output typeReal code application (Text to App type)Configuration-based application (Web App, Mobile App, etc.)
Ongoing editing environmentCode builder (chat interface)No-code Page Builder
Best forCustom logic, complex data transformations, developer-driven workflowsStandard CRUD apps, dashboards, forms, low-code workflows
AI involvementAI writes and iterates the full codebase on requestAI can assist with individual component suggestions

How to Start a Code-First App

The code builder is accessed through the AI creation screen, which appears when the AI builder feature is enabled for your workspace. If both build modes are enabled, a Code | Config toggle above the prompt box picks between them. Code is selected by default. See Config-First App Creation for the Config mode.

Steps: Starting a Code-First App

  1. Open the Applications Manager and click New Application. The AI creation screen opens (requires AI builder to be enabled for your workspace).

  2. Make sure Code is selected in the toggle above the prompt box. Code is the default. If Config is selected, click Code.

  3. Type a description of the application you want to build — be as specific as you need. For example: "Build a project tracker with a Kanban board, task detail panel, and due-date filtering."

  4. Send the prompt. The code builder generates the application from your prompt. The app is listed in the Applications Manager as type Text to App right away.

  5. The code builder opens in a chat interface. Review the generated app, then continue refining it by sending follow-up prompts: add features, fix issues, or change the layout.

  6. When you want the app live at its Application URL, publish it from within the code builder. See Publishing a Code App below.

The prompt box also has these controls:

  • Auto / Plan — Auto (the default) lets the agent decide how to build. Plan has the agent discuss a plan with you before building.

  • Model picker — the AI model the code builder uses.

  • Design system — pick a theme or design system for the new app.

  • Attach file — add files or screenshots to your prompt. You can also paste or drop an image.

  • Microphone — dictate your prompt instead of typing, where your browser supports it.

Note: Text to App apps are edited in the code builder, not the no-code page builder. Clicking a code app in the Applications Manager opens its Overview tab, like any other app. Click Open in Builder to return to the code builder chat. All future edits happen through the code builder.

The Text to App Entry

When the code builder creates an application, it is registered in the Applications Manager with the type tag Text to App. This distinguishes it from manually created app types (Web App, Mobile App, etc.) and signals to the platform that the app's canonical editing environment is the code builder, not the page builder.

  • Clicking the app name in the Applications Manager opens the app's Overview tab. Use Open in Builder to get to the code builder.

  • Row actions (Edit Details, Clone, Share, Delete) work the same as for other app types.

  • Type is fixed — a Text to App cannot be converted to a Web App or Mobile App.

Working in the Code Builder

After the app is created, you keep building it by chatting with the agent in the code builder:

  • Chat — describe a change in the composer. For anything substantial, the agent proposes a plan first. Click Review to read it, then Approve to build it or Skip to decline it.

  • Preview — the app runs live in the builder, so you can check each change as the agent makes it.

  • Saved versions — every change the agent makes is saved automatically as a version. Open More › Saved versions to preview an earlier version and click Restore this version to go back to it.

  • Git — optionally link the app to a new GitHub repository or GitLab project from More › Git. You can then develop in parallel branches and review changes with pull requests before they go live.

Publishing a Code App

  1. In the code builder, open the Preview tab and click Publish in the header.

  2. Optionally, enter a version tag in Tag this version and describe the changes in Version notes.

  3. Click Publish. The app is built and released at its Application URL.

Publish is unavailable until the app has been built at least once, and while you are on a branch other than the app's default branch. If the published app already matches the current code, the button reads Up to date.

The Code App's Pages

Clicking a code app in the Applications Manager opens its pages:

  • Overview — a live preview of the app and a Details panel with the Application URL, Application ID and tags.

  • Insights — usage analytics for this app.

  • Tests — shown only if you have permission to view tests.

  • Versions — every published version. Open one to see a read-only preview of that release.

  • Settings — the app's settings.

Use Open in Builder in the header to return to the chat and preview workspace, or Preview to open the running app in a new tab.

FAQs

Do I need programming knowledge to use code-first app creation?

Yes. Code-first creation (the Code build mode) is aimed at developers and technical users who want to express application logic in code or prototype quickly with AI assistance. The resulting app is a genuine code application edited through a chat-based code builder. If you prefer to build without writing code, use the Config build mode (described in Config-First App Creation), which opens the visual no-code page builder instead.

What languages or frameworks does the code builder support?

The code builder generates applications using UnifyApps' internal code application framework. The AI writes and iterates the full codebase in response to your natural-language prompts. For specifics on the supported runtime, language, and framework versions, refer to the code builder documentation or contact UnifyApps support, as this may vary based on your workspace configuration.

Can I test a code-first app locally before publishing it?

Code-first (Text to App) applications are built and run within the code builder's chat interface. Local development outside the platform is not part of the standard workflow. You iterate on the app by sending follow-up prompts in the code builder and reviewing the generated result there. Publishing from the code builder makes the app live at its Application URL, which is the primary way to share a finished version with users.

Can I integrate a code-first app with a CI/CD pipeline?

You can link a code app to a new GitHub repository or GitLab project from More › Git in the code builder. The app's source is then kept in your own repository, and you can develop in parallel branches and review changes with pull requests before they go live. For automated deployment workflows beyond this, contact your UnifyApps account team to discuss available options.

What is the Interface Record and why does it matter for code-first apps?

The Interface Record is the underlying data structure that stores every application's identity, type, navigation, theme, security rules, and app-level configuration. Regardless of whether an app was created code-first or config-first, it is stored as an Interface Record. Understanding it explains why certain settings — like app type — are fixed after creation, and why app-level variables and navigation are configured in a central place rather than scattered across individual pages.