Data, sign-in, and integrations
Understand what your app needs beyond its interface, and how to describe those requirements.
Choose how your app saves data
Tell Bump AI what records your app should store and how they relate. A personal prototype may use browser storage; a shared product usually needs a backend that makes data available across users and devices.
Specify who can read, create, update, and delete records. Ask the builder to explain the chosen storage approach and any configuration required before launch.
Your app’s users have their own sign-in
Your Bump AI account gives you access to the builder. People using the app you create need that app’s own authentication if its features require accounts.
Describe registration, sign-in, sign-out, account recovery, and any user roles. Test account access with separate users and check server-side permissions for private records.
Connect external services deliberately
Payments, email, calendars, and external APIs may need a separate provider account, credentials, setup, and usage fees. Ask Bump AI to identify what the app needs, then complete the relevant service configuration.
Available connections depend on the app and the supported integration path. Check the actual options in your project; a service mentioned in an example is not a promise of a built-in connector.
BYOK is for building your app
Bring your own key (BYOK) chooses the AI provider used by Bump AI while building. It does not automatically add AI features, payment processing, or other services to the app you publish. Those are separate integrations. Learn how BYOK and runtime credits work.
Check the complete workflow
- 1
Create and retrieve a real record
Save something, refresh, and confirm that the intended user can retrieve it.
- 2
Try the wrong user
Confirm that another account cannot read or modify private records it does not own.
- 3
Test failures
Check invalid form inputs, failed requests, empty lists, and interrupted connections.
- 4
Verify the live configuration
Check the published app’s service settings and URLs. A working development connection may need separate production configuration.