Storage & Database
LaunchPulse gives every project a built-in place to manage app data. Use Storage for uploaded files, images, documents, and media. Use Database for structured app data such as users, profiles, products, game progress, orders, messages, bookings, and records.Storage is for files. Database is for structured data. Most real apps need both.
What Storage & Database are for
Storage
Store and manage uploaded files, images, documents, avatars, screenshots, PDFs, and other media used by your app.
Database
View and manage structured app data such as users, tables, records, product catalogs, game scores, tasks, orders, and customer information.
Storage vs Database
| Use this | When you need to store | Examples |
|---|---|---|
| Storage | Files and media | Profile pictures, PDFs, images, screenshots, videos, uploaded documents |
| Database | Structured records | Users, tasks, orders, bookings, products, messages, game progress |
| Both | Files connected to records | User avatar linked to a user profile, product image linked to a product, document linked to a client record |
How LaunchPulse handles app data
LaunchPulse is designed so users do not need to manually set up storage and database infrastructure from scratch. When your app needs persistent data, LaunchPulse can help create the right structure and connect it to your project.Describe what your app needs to remember
Tell LaunchPulse what data should persist, such as users, posts, orders, bookings, uploaded images, game progress, or saved AI outputs.
LaunchPulse creates the structure
LaunchPulse can create the database tables, storage upload areas, and the app logic needed to save and retrieve data.
Manage data from the project workspace
Use the Storage and Database panels to inspect files, view tables, check records, and understand how your app data is organized.
Storage
Storage lets your app accept and manage uploaded files. Use Storage for:- profile avatars
- app screenshots
- user-uploaded documents
- images and media
- PDFs
- attachments
- product photos
- generated files
- downloadable assets
What the Storage panel shows
The Storage panel helps you understand how much file storage your project is using. You can see:- storage usage
- number of files stored
- storage quota
- upload area
- existing uploaded files
- file buckets when users upload files
Your current workspace shows a 100 MB quota and a 50 MB max file size per upload. These limits may vary by plan or future product updates.
Example Storage use cases
User avatars
Let users upload profile photos and store them safely in the project.
Product images
Store images for ecommerce products, listings, marketplaces, or catalogs.
Documents
Allow users to upload PDFs, forms, contracts, resumes, or files.
Generated assets
Save AI-generated files, exports, screenshots, or reports.
Mobile app media
Store uploaded images, game assets, or user-generated content.
Internal tools
Attach files to customers, tasks, tickets, approvals, or records.
Database
The Database panel lets you inspect structured app data. Use Database for:- users
- profiles
- projects
- tasks
- orders
- products
- bookings
- messages
- comments
- subscriptions
- game characters
- achievements
- scores
- saved AI outputs
- workflow records
What the Database panel shows
The Database panel lets you view tables and inspect app data. You can see:- database tables
- row counts
- column counts
- selected table data
- app records
- structured data created by the app
- characters
- achievements
- goals
- quest completions
- milestones
- users
- users
- organizations
- subscriptions
- projects
- invoices
- messages
- settings
Storage and Database together
Many real apps need both storage and database.| App feature | Storage role | Database role |
|---|---|---|
| Profile avatar | Stores the uploaded image | Stores the user profile and image reference |
| Product catalog | Stores product images | Stores product name, price, category, and stock |
| Client portal | Stores documents and attachments | Stores client records, tasks, and permissions |
| Mobile game | Stores media or generated assets | Stores characters, progress, scores, and unlocks |
| AI app | Stores exported files | Stores prompts, results, saved outputs, and usage history |
| Marketplace | Stores listing images | Stores listings, users, messages, bookings, and payments |
When your app needs a database
Your app probably needs a database if users need to:- sign in
- save progress
- create accounts
- manage profiles
- save records
- view history
- search or filter data
- edit information later
- access the same data across devices
- share data with other users
- manage admin dashboards
- track payments or subscriptions
When your app needs storage
Your app probably needs storage if users need to:- upload images
- upload documents
- save profile pictures
- attach files to records
- upload screenshots
- store generated files
- manage media
- save exports
- share downloadable files
Common data patterns
User profiles
Store user details in the database and avatar images in storage.
Admin dashboards
Store records in tables so admins can view, filter, update, and manage data.
Marketplaces
Store listing images in storage and listing data in database tables.
Games
Store player progress, characters, scores, achievements, and unlocks in the database.
AI tools
Store prompts, generated outputs, saved results, and file exports.
Internal tools
Store clients, approvals, documents, notes, statuses, and activity history.
Example prompt: add user avatars
Example prompt: add persistent app data
Example prompt: add files to records
Example prompt: add game progress
Best practices
| Best practice | Why it matters |
|---|---|
| Store files in Storage | Keeps large uploads separate from structured app records |
| Store records in Database | Makes data searchable, editable, and connected |
| Link files to records | Keeps uploaded files connected to the right user, product, or task |
| Use safe demo data | Avoid exposing private customer information |
| Add empty states | Users should know what to do when no data exists yet |
| Add error states | Upload or database failures should be clear |
| Test after refresh | Confirms that data is truly persistent |
| Keep permissions clear | Users should only access data they are allowed to see |
Common mistakes
| Mistake | Better approach |
|---|---|
| Saving uploaded files only in the browser | Use Storage so files persist |
| Saving app records only in local state | Use Database so records survive refresh |
| Mixing files and structured records | Store files in Storage and metadata in Database |
| No upload validation | Add size, type, and error handling |
| No empty states | Explain what users should do when there are no files or records |
| No permission checks | Make sure users only see their own data unless intended |
| No fallback UI | Add placeholders for missing images or empty tables |
Storage checklist
Before launching a feature that uses Storage, check:- files upload correctly
- file size limits are handled
- unsupported file types show an error
- uploaded files appear in the app
- files stay available after refresh
- private files are not exposed publicly
- users can remove files if needed
- fallback UI exists when no file is uploaded
Database checklist
Before launching a feature that uses Database, check:- records save correctly
- records load after refresh
- edit and delete actions work
- empty states are clear
- error states are handled
- user permissions are correct
- tables are named clearly
- test data does not expose private information
Strong follow-up prompts
Add storage uploads
Add database persistence
Connect storage and database
Review data model
Next steps
Authentication
Add sign-up, login, users, and account access before saving user-specific data.
AI Services
Store AI prompts, generated outputs, saved results, and user history.
Payments & Monetisation
Store subscription status, billing states, and paid access logic.
Build an Internal Tool
Create dashboards with tables, records, filters, and file attachments.
Web App Development
Build web apps that use persistent data, uploads, and user records.
Mobile App Development
Build mobile apps that save user progress, media, and structured records.
Frequently asked questions
Does my LaunchPulse app keep data permanently?
Does my LaunchPulse app keep data permanently?
Yes. LaunchPulse builds a real database, so records, user data and files persist between sessions rather than resetting on reload.
Can my app store files and images?
Can my app store files and images?
Yes. You can add file storage for uploads such as images and documents by prompting for it.
How do I keep each user's data private?
How do I keep each user's data private?
Combine storage with authentication and scope records to the user who created them, so people only see their own data.
Do I need to design the database myself?
Do I need to design the database myself?
No. Describe the records and relationships in plain language and LaunchPulse builds the data model and connects it to your app.
Can stored data power AI features?
Can stored data power AI features?
Yes. Stored records can feed AI services like search, generation and assistants, so your data works with your AI features.
How do I link records together?
How do I link records together?
Describe the relationship in your prompt, for example “each order belongs to a customer”. LaunchPulse builds the link so you can look records up across the app.
How much data should I model at the start?
How much data should I model at the start?
Only what your core workflow needs. Add fields and records later as the app grows, rather than modelling everything upfront.
Add AI features to your data
Turn stored data into smart features. Explore AI services like search, generation and assistants.