Deployment on Rofy
Learn how to preview, test, and deploy your application on Rofy so it can be shared with the world.
Deployment on Rofy
The ultimate goal of building an application on Rofy is to launch it and share it with users.
Rofy provides a simple workflow that allows you to preview your application, test it, and deploy it to production.
Deployment Workflow
Here are the main steps involved in launching your application.
1. Pre-Deployment Health Check
Before deploying your application, it's recommended to verify that everything works correctly.
Things to check:
- UI and layout
- Feature functionality
- API responses
- Navigation and routing
- Error handling
Testing beforehand helps avoid deploying broken or incomplete features.
2. Deployment
Once your application is ready, you can deploy it to make it publicly accessible.
Deployment provides:
- A permanent public URL
- 24/7 uptime
- Production infrastructure
- SSL security
- Custom domain support
After deployment, your application can be accessed by users, customers, or team members anywhere in the world.
Previewing Your Application
Rofy provides a Preview Mode so you can test your application before deploying it.
Preview allows you to:
- View your app's current state
- Test functionality
- Iterate on design and features
- Debug problems before release
Preview links are temporary and typically expire after 30 minutes.
This ensures resources are used efficiently during development.
How to Preview Your App
- Click the Preview button in the Rofy interface.
- A preview window will open with your current application state.
- Interact with the application to test features.
- When code changes are made, the preview automatically updates.
Preview mode is ideal for testing and iterating quickly during development.
Tip: Use preview mode to verify that every component works correctly before deploying your application.
Preview Mode vs Deployed Mode
There are important differences between Preview Mode and Deployment Mode.
| Aspect | Preview Mode | Deployed Mode |
|---|---|---|
| Purpose | Testing environment | Production environment |
| Accessibility | Only you can access | Public URL |
| Persistence | Temporary | Permanent |
| When to Use | Development & testing | When app is ready for users |
| Changes | Live updates | Requires redeployment |
| URL | Temporary preview link | Permanent public URL |
| Cost | Free | Uses deployment credits |
Key Differences Explained
1. Accessibility
Preview Mode
Preview generates a temporary URL such as:
Characteristics:
- Only works while the preview session is active
- Private to your development session
- Best for internal testing
Example use case:
"Check this preview link to review the latest changes."
Deployed Mode
Deployment generates a permanent URL, such as:
Characteristics:
- Only works while the preview session is active
- Private to your development session
- Best for internal testing
Example use case:
"Check this preview link to review the latest changes."
Deployed Mode
Deployment generates a permanent URL, such as:
Characteristics:
- Only works while the preview session is active
- Private to your development session
- Best for internal testing
Example use case:
"Check this preview link to review the latest changes."
Deployed Mode
Deployment generates a permanent URL, such as:
Characteristics:
- Only works while the preview session is active
- Private to your development session
- Best for internal testing
Example use case:
"Check this preview link to review the latest changes."
Deployed Mode
Deployment generates a permanent URL, such as:
or a custom domain.
Characteristics:
- Accessible 24/7
- Publicly available
- Suitable for real users
Example use case:
"Our application is live — visit the website!"
2. Updates & Changes
Preview Mode
Changes appear instantly.
Example workflow:
- Change a UI element
- Save the code
- Refresh preview
- See the update immediately
This is ideal for rapid development and iteration.
Deployed Mode
Changes require redeployment.
Example workflow:
- Update the code
- Deploy a new version
- Users see the updated application
This ensures stability for users.
3. Purpose & Intent
Preview Mode
Used for:
- Testing features
- Identifying bugs
- UI experimentation
- Debugging problems
Preview is a safe environment where issues won't affect real users.
Deployment Mode
Used when your app is ready for real users.
Characteristics:
- Production environment
- Stable and reliable
- Publicly accessible
- Represents your product or business
Issues in production may affect real users, so testing beforehand is important.
Troubleshooting Before Deployment
If something doesn't work correctly during preview, you can troubleshoot before going live.
Common checks include:
- Verify API connections
- Check console errors
- Confirm environment variables
- Ensure routes and navigation work
- Test user interactions
Resolving issues in preview ensures your deployed application runs smoothly.
Best Practices Before Deploying
Before launching your app:
- Test all major features
- Verify mobile responsiveness
- Check error handling
- Confirm API responses
- Ensure UI elements load properly
Doing these checks helps create a stable production release.
Ready to Launch
Once everything looks good in preview mode, you can deploy your application and share it with the world.
Your deployed application will be:
- Publicly accessible
- Available 24/7
- Ready for real users