Skip to documentation
Docs Getting started
On this page 6 sections

Start here

Getting started

Go from first launch to a useful first app, then make one improvement.

Name your first app

On first launch, Zymorph opens Name it and choose its design.

  1. Choose a clear name. Use the purpose of the app, such as “Studio Desk” or “Supply List.” You can rename it later.

  2. Choose a design. This is only the visual starting point. You can change it after the app exists.

  3. Select Continue.

First launch with the app name and design choices First launch asks for a name and visual starting point—not a technical setup.

Zymorph may briefly prepare the app on this computer. Keep the app open while that finishes. This is normally a one-time step for the device.

Connect a model

Zymorph needs an AI model to understand requests and create or change an app. Model access is not included, so connect your own supported subscription or API key:

  1. Select Open Model providers when the conversation asks you to connect a model.
  2. Sign in with a supported subscription or select Add API key.
  3. Complete the provider’s instructions, then return to the app.

Anthropic Pro and Max plans include Claude Code, and Zymorph supports signing in with those plans. That use counts against the plan limits shared by Claude and Claude Code. If you add an Anthropic API key instead, usage is billed separately through your Anthropic Console account.

With any provider API key, the provider bills usage according to its API plan. The key belongs in Settings → Model providers, never in the conversation. See Model providers for the full subscription and BYOK explanation.

Your request leaves the device When you ask Zymorph to create or change an app, the request and relevant working context go to the selected model provider. Review that provider’s privacy and billing terms before connecting it.

Describe one useful app

Describe the app’s purpose and the information it should keep. For example:

Create a simple studio supply list. I need an item name, quantity, low-stock warning, and notes.

A useful first request usually says:

  • what the app should help you accomplish
  • which information the app should keep

A focused first request in the conversation composer Describe the outcome. Zymorph decides how to build the first version.

Press Return or select Send. Use Shift + Return when you want a new line without sending.

Wait for the first version

While Zymorph works, the conversation shows progress. The app preview on the right dims and a morphing shape appears in its center. The time varies with the request and model.

  • Keep Zymorph open while it works.
  • Select Stop if you sent the wrong request or no longer want it to continue.
  • An error does not mean your existing app data was deleted. Read the message and try the suggested action.

When it finishes, use the app on the right. Add a sample item, search, change a quantity, and reopen the app if persistence matters to you.

A working supply-list app ready to try Use the first version before asking for more. Real use reveals the most useful next change.

Ask for one improvement

Return to the conversation and describe one result you want. For example:

  • “Put low-stock items at the top.”
  • “Make the notes easier to read.”
  • “Add a filter for items I need to order.”

What happens next

The first version is not a final delivery. A normal Zymorph workflow is:

  1. Describe a need.
  2. Try the result.
  3. Notice what would make it more useful.
  4. Ask for that change.

Continue with The Zymorph interface for a complete tour, or Create a useful app for help planning a stronger first request.