Build your first app. In one touch.
Fusion is the AI app builder built into Flip. Describe the app your team needs in plain language. Fusion builds it as a native Flip app. You ship it to your entire frontline in one touch.
Before you start
|
✓Fusion open and ready. You’ll find Fusion in your Flip Admin Console: its own item in the left navigation, right below the existing menu items. Building requires builder rights, granted by your admin.
✓A real use case. Start small. A form, a checklist, an overview. Something your team asks for today.
✓Assets to start from. Anything that shows what you need: a photo of a paper form or whiteboard, a screenshot of a spreadsheet, an existing document. Fusion can pick it up and replicate it.
|
1Describe
Describing is most of the work, and it’s the part you already know how to do. Brief Fusion the way you would brief a colleague. Two moves: plan, then build the prompt.
1.1Plan your app
The best Fusion apps are planned in four questions, not forty. Two minutes, on paper:
01
What does the app do?
One sentence. A handover form, a KPI dashboard, a booking tool, a daily overview.
|
02
Who uses it?
Who works with it, and in which roles? Use roles and groups that already exist in your Flip environment.
|
03
What data and integrations does it need?
Fusion already knows your people, roles, locations and shifts. Name what else: records your app creates, or sources it reads.
|
04
How does a user move through it?
One screen that displays data, or multiple screens with a flow? Sketch what the user sees and does, from opening the app to done.
|
| That’s the whole plan. Fusion handles the how: architecture, design, integration, security. |
1.2Build your prompt
Turn your plan into one message, written the way you would brief a colleague: plain language, no technical vocabulary. If you can write a clear chat message, you can build a Fusion app. Cover the four planning questions, attach your starting assets, and send it. You can refine everything later in the chat.
Say who and what
Who uses the app, and what it must do. Fusion handles the how.
|
Attach what exists
A photo, a screenshot, a document. Your starting assets save you describing every detail.
|
Name your data sources
Pull from Flip, store in the app, or read an external source. Explicit beats implicit.
|
Tips for good prompting in Flip Fusion
- Start small: Keep your first prompt short and simple. Describe the basic app first, then add everything else step by step.
- Name users and roles: Who uses the app? Who sees what? If there should be an admin area, state clearly who should have access (e.g. system administrators).
- Iterate step by step: Ideally, include only one change per prompt and refine specifically (“Add … to the start screen”) — this keeps changes traceable and makes errors easier to find.
- Edit specific spots: If you want to change something in a specific place, select “Edit element” in the toolbar above the Fusion app to click directly on that spot.
- Define what happens after actions: What happens after submitting? (Confirmation + where does the user return to?)
- Think mobile first: Frontline users are on their phones — keep it simple, few taps, large buttons.
- Feed errors back: Simply copy or screenshot error messages and give them to Fusion with a request to fix them — the AI can work with that directly.
| Want a sharper prompt? Run your draft through any AI chat tool you already use, like ChatGPT or Claude, and ask it to structure and sharpen your description before you paste it into Fusion. |
2Build
Send the prompt. From here, Fusion does the heavy lifting. You watch, test, and steer.
2.1Let Fusion build
Right after you send the prompt, Fusion plays its understanding back to you: a short summary of what it will build: screens, behaviors, assumptions. Accept it, or adjust anything that’s off, right there in the chat. Then Fusion builds: it integrates the app with Flip’s APIs, writes the code and checks that everything works.
| Native from the first second. Every app Fusion builds is a Flip app. Authenticated for every worker, role-aware, mobile-first and offline-ready. Nothing to bolt on later. |
2.2Preview your app
Try the app in the live preview, exactly as your team will see it on their phones. Tap through it like a worker would: fill the form, submit an entry, check the result. The preview runs as you, the signed-in user, with your role and permissions.
2.3Refine in plain language
Want changes? Say so in the chat. “Make the buttons green” is a valid instruction. Refining is the same conversation as building. Every completed change creates a version in your history, with a Restore button next to it. One click brings any earlier version back, so you can experiment freely.
| A good rhythm: ship the smallest version that solves the problem, then refine with real feedback from your team. |
3Ship
Building and shipping are the same action. Three moves: publish, choose who sees it, and update anytime.
3.1Ship in one touch
Happy with it? Click “Publish”. No app store, no MDM rollout, no IT ticket queue. Your app is live: private to your Flip environment, with workers signed in automatically through their Flip profile.
3.2Choose who sees it
Click “Add menu item” in the popup, or add it later via the menu settings. Pick a name, an icon and how it opens, then set the visibility: which user groups see the menu tile, and on which platforms. This is Flip’s standard menu item editing, the same process your admin uses for every other tile.
3.3Update anytime
Need changes later? Jump back into the editor and keep working. Your edits stay invisible to your team: the live app keeps running unchanged while you optimize in the background. When the new version is ready, click “Publish” again. That’s it. The updated app is in everyone’s hands, and your team needs to do nothing.
🚀 Live for your entire frontline.
That’s it. The app appears for every assigned worker, right in the Flip menu next to everything else your team uses.
| Your team needs to do nothing. No download, no registration, no new login. The app works for workers without a company email, on shared devices and personal phones, online or offline. If they can open Flip, they can open your app. |
What will you build next?
Real apps already built with Fusion: Shift Handover (Ops) · Employee Pulse Survey (HR) · Plant KPI Health (Ops) · Ride to Work / Carpool (Ops) · Employee Benefits (HR) · Canteen Menu (Ops)
Good to know
- Compliant by architecture. Every app inherits Flip’s compliance posture. EU data residency, GDPR, ISO 27001 and Works Council readiness. No new DPA, no fresh approval round per app.
- Governed by design. IT/admins keep full control of who gets builder rights. Every app inherits the same architecture, identity and integrations. Consistency is structural.
- Part of Flip. Fusion is built into the Flip platform, so identity, access and distribution are already solved. If a worker can open Flip, they can open your app.
|
Don’t see Fusion yet?
Fusion rolls out guided. We’ll build your first app together, live in one session. You bring the use case, we bring Fusion.
|