Own your app

2.1 Determine if your app should be exported

Open the app you built earlier — your Lovable task tracker or Base44 booking app — to decide if it’s time to leave the platform based on concrete signals.

Identify whether your AI‑built app has outgrown the platform

Paste the prompt into the Prompt field of the claude-code interface and press Run. Verify that the returned table lists all six signals exactly as written; any missing rows means the analysis didn’t cover a signal.

1. Open the published version of your app from the Published apps list and use it for two minutes as a typical user would
2. Review each of the six signals described in the next section and mark each one hit or not hit for your app
3. Count the number of hits; if you record 0–1, keep using the platform, but if you record 2 or more, plan to export the code

• You'll see A number indicating how many of the six signals your app meets
• Takeaway A checklist shows when an app needs its own code rather than staying on the platform
• Check How many of the six signals must your app hit before you plan to export the code rather than stay on the platform?

2.2 Explore the Nextcloud Developer Resources

The Nextcloud App Store includes a developer section that lists tools and documentation for building apps on the platform.

You will locate and open the developer documentation page for Nextcloud so you can reference it later when exporting an app.

1. Open a web browser and go to https://apps.nextcloud.com/.
2. Click the menu item labeled “Resources for developers”.
3. Select “Develop for Nextcloud” from the dropdown list.
4. Read the brief description and note the link to the full developer documentation.
5. Bookmark the documentation page in your browser.

• You'll see The browser displays a page titled “Developer documentation” with links to API references, translation tools, and app submission guidelines.
• Takeaway Knowing where official development docs live lets you transition from a no‑code builder to custom code when needed.

2.3 Deploy a Simple Node.js App on Google App Engine

Google Cloud’s App Engine is a fully managed platform that runs applications written in languages like Node.js.

You will create, configure, and deploy a minimal Node.js web app to the App Engine standard environment.

1. Open the Google Cloud console and start a new project (or select an existing one).
2. Create a file named app.js with the following content: const http = require('http'); http.createServer((req, res) => { res.write('Hello from App Engine'); res.end(); }).listen(process.env.PORT || 8080);
3. Create a package.json file that specifies `

• You'll see The Cloud console shows the new version of your service as ‘Serving’, and visiting the provided URL displays “Hello from App Engine”.
• Takeaway App Engine lets you move an exported app onto infrastructure you control without managing servers.

2.4 Run your exported app in a GitHub Codespace

Open the repository saved by the builder on GitHub and launch a cloud‑based workspace that runs your exported project independently.

Do this first Determine if your app should be exported

Open the exported project in a cloud‑based workspace you control

git clone https://github.com/<you>/<your-app>.git
cd <your-app>
npm install
npm run dev

Paste this into the claude-code input field on the main screen and press Run. Watch for the provisioning messages—once the Codespace is ready, the terminal will show the server URL you can open in a browser.

1. Open the repository saved by the builder on github.com (e.g., your-name/task-tracker)
2. Click the green Code button → select Codespaces → choose Create codespace on main and wait for the environment to initialise
3. Observe the code editor that appears with your app’s files listed in the left pane
4. If a Preview panel does not appear automatically, click the Open in Browser pop‑up to view the running app at its own web address

• You'll see Your app loads at a web address that belongs to your own GitHub repository
• Takeaway A Codespace provides an independent, browser‑based environment where the code runs under your ownership
• Check Which button on the repository page starts a codespace, and what appears once the environment has initialised?

2.5 Make a code change using Claude Code

Use Claude Code inside your workspace to describe a feature change; review the proposed edits before they are applied.

Do this first Run your exported app in a GitHub Codespace

Add a new feature to your app with Claude Code

Paste the sentence into the Claude Code input box in your workspace Terminal, then wait for Claude to display the list of files it will modify. Verify the proposed changes before clicking Approve; watch that only the intended task‑related files are listed.

1. Open the Terminal in your workspace and start Claude Code
2. Tell Claude Code what you want to add, e.g., a priority badge for tasks
3. Read the proposed file changes and confirm the edit
4. Refresh the Preview to observe the new feature
5. If the result is incorrect, explain the issue in plain words and repeat

• You'll see The app displays the added priority badge after you approve the file edits and refresh the preview
• Takeaway Describe a single feature, review exact file edits, and see the change instantly
• Check What do you read and approve before Claude Code's change reaches your app, and how do you then see it?