Building your software

You don’t need to become a developer. Start with one useful job, try it, and build from there. Use Codex, Cursor, Claude or your preferred builder; your project stays yours.

Start with a coaching decision#

Describe who will use the tool, what they need to decide and what they should be able to do next. One clear job is a better starting point than a long list of features.

Try this in your builder:

Build a dashboard that helps me decide which riders need my attention today. Show all riders together, explain why someone is flagged and let me open their recent activity. Start with clearly labelled example data. Ask me only what you need to make the first useful version.

Give a screenshot or a reference when the visual style matters. Say what you like about it: the layout, the clarity of the charts or how quickly you can scan it. You can change the design later.

Know what is real#

A convincing chart can still be showing example data. Ask your builder to label the data source and explain what is connected.

Inspect this project’s MovePacket capabilities. Use MovePacket Data Connect as the intended athlete data source. Tell me what access is available and what is missing. Keep example data labelled until a real connection is working. Don’t put athlete records or keys into the page source.

The current project builder connection does not itself grant access to the athlete library. Connecting real data needs the appropriate permission and a supported server-side path. Uploading a file into a temporary browser preview does not necessarily save it to MovePacket.

Change one useful thing at a time#

Say what the result should do, rather than trying to name the technology.

Keep the existing dashboard. Add a way to sort riders by who needs attention, and explain each flag using the available evidence. Show missing information instead of inventing a score. Keep the rest of the behaviour working.

Ask the builder to explain any extra service, charge or permission before adding it. Keep API keys out of chat and generated pages. Use MovePacket’s supported connection flow where available.

Preview before making it live#

There are two places to try a change. Your builder’s local preview is for quick experiments. The private MovePacket preview is a saved version you can review before publishing.

Test this change, save it as a MovePacket update and give me its private preview link. Tell me what changed, what you tested and anything that still needs checking. Leave the live version as it is until I approve.

Try the actual task: choose a rider, change a filter, check a chart and see how missing data is handled. The preview is not connected to live records, payments or email. Features that depend on those services need separate testing.

Make the version you checked live#

In your project’s Updates view, open Preview changes, review it, then choose Make live. Publication keeps the project’s current audience: a private project stays private; a public project remains public.

If your builder says another version is already live, ask it to bring the changes together and save a new update. Do not ask it to skip the conflict.

Publish the exact version I approved, preserve the project’s access setting, then help me check the result at my project address.

Open the live app and try the main task again. A successful upload is not proof that every feature works.

Know how to recover#

MovePacket keeps previous published application versions available to restore. Restoring files does not reverse database changes, messages sent or payments made.

Before changing sign-in, data storage or payments, explain what could be affected, how we will test it and how we would recover. Check which protections and backups are actually active for this project.

You decide the coaching workflow, design and audience. Your builder changes the application. MovePacket provides the supported infrastructure, access controls and saved-version workflow. Check each service’s status in your project; don’t assume every possible integration or protection is connected automatically.

For your builder’s commands and current limits, see Build with AI.