From data and models to an app people can use
Build the product around your data-science work. Describe what people need to do, connect project data or a supported model, and develop a working application with OctOpus. The Apps studio brings Preview, Code, Data and saved versions together so you can shape the experience and publish it to the intended audience.
Start with the user’s task
Describe who will use the app and the action they need to complete. A planning tool could show a product forecast; a voice app could turn text into speech. Include the inputs, expected result and information people need to act on it. This gives the build a concrete purpose.
Bring your project data into the experience
Import project data or a file, then use the app’s Data view to inspect the records and collections behind the interface. Build useful actions around that information: browse a catalogue, explore a customer segment or review a forecast. Keep the source and the application data connected to the same project.
Put a model to work in the app
Connect a supported model when the user’s task needs predictions, generated speech or another model output. Define how the app collects inputs and presents the result. A forecasting tool, for example, can pair a model response with historical data and the assumptions people need to understand before making a decision.
Build and refine in the studio
Ask for the application or a focused change through the project chat. Open the saved version in Preview, inspect or edit its source in Code, and explore its records in Data. Use saved versions to compare changes or restore an earlier version as you refine the layout and main user flow.
Check the main flow and publish
Try the app with representative inputs, verify the model binding when one is used, and review data freshness and permissions. Choose the intended audience with the publishing controls. Keep model evaluation separate from app access: the model should suit the task, and each visitor should see and change only the intended information.
Keep improving from the same project
Continue the conversation with a specific improvement: a clearer chart, an additional input or a simpler result screen. The project keeps the app version close to its data, model results and source code. That context helps you reproduce the main flow and carry what you learn into the next version.
Key capabilities
- A working app preview with inspectable source code.
- Project data, app records and supported model connections.
- Saved versions and focused conversational changes.
- Publishing controls for the intended audience.
Frequently asked questions
Can I build an app without first training a model?
Yes. An app may use project data without a trained model. If its main action requires prediction or speech generation, connect a supported model or service and test that action explicitly.
Does a completed build mean the app is production-ready?
It means a version was saved. Review the generated code, user flow, permissions, data freshness and model behavior before publishing it to the intended audience.
Can I inspect and change the code?
The Apps studio exposes the saved source in its Code view. You can inspect it, make edits and save a version, or ask for a targeted change through the project chat.