Reviewed · Published by RiverX
Turn a brief into a working user journey
Start with the person using the app, the action they need to take and the result they should see. For example: a customer submits a service request, receives confirmation and can return to see its status. Include representative fields, validation and an empty state. A small complete journey is easier to evaluate than a list of disconnected screens.
Choose the starting point and the model
Start from a template when its structure fits, or describe a new project. RiverX's model directory exposes provider names, capabilities, context windows and recorded pricing where available. Skills provide reusable instructions for an agent. A template is a starting codebase, a skill is guidance, and a model performs AI work; choosing one does not substitute for configuring the others.
Connect data and verify behavior
RiverX includes database provisioning and a live preview. Use those to test a real save-and-reload cycle, invalid inputs and access to another user's records. If an integration needs credentials, keep them out of public source and browser-delivered code. Inspect the generated project and its dependencies before using real customer data.
Publish, then test the published application
Publishing is part of the RiverX workflow. After publishing, repeat the core journey at the live URL, inspect environment-dependent behavior and check a phone-sized screen. Review keyboard access, labels, focus and readable contrast against accessibility requirements. Decide who will monitor errors and maintain the app after launch.
Sources: W3C accessibility requirements
Understand what you are paying for
RiverX uses a free allowance for eligible free-tier usage and a wallet for paid usage. Adding funds switches the account from the free allowance to metered billing. The credit added, top-up fee and applicable tax are different quantities. Use current pricing and actual usage records to budget; a catalog's provider token price is not a quote for a finished app.
Start with a real project
Explore published templates, then make the application your own.
Find your way to build
Explore the workflow, model choices and handoff that fit your project.
What can I build with RiverX?
RiverX's public scope covers websites and web applications, with templates, selectable models, coding agents, preview, database provisioning and publishing. Confirm any special runtime or integration requirement before committing to it.
Do I need to start from a template?
No. A template gives you an existing project structure when it fits your brief. Review its technology and source before choosing it, or describe the application you want to build.
Does generated code mean the app is production-ready?
No. Production readiness depends on verified behavior, authorization, data handling, accessibility, deployment configuration and ongoing maintenance.
Does RiverX provide a public API or MCP integration?
A product API or MCP integration is not advertised here. The AI-readable resources are public product and catalog content, not a way to operate the builder or private projects.
Put the pieces together
Models, instructions and starting points for your next project.