Build and Run the Application
The user first generates, builds, and runs the application using Mayson.
Deploy the Application
After the application runs successfully, the user must click the Deploy button. Deployment is required before any subdomain configuration becomes available.
Default Subdomain Assignment
Once deployment is successful, Mayson automatically assigns a default subdomain to the user.
Open Subdomain Settings
When the user clicks the Deploy button again, an input box appears with the default subdomain already prefilled.
Edit the Subdomain
The user clicks the Edit (pencil icon) to enable editing and replace the default subdomain with their own custom subdomain.
Confirm Custom Subdomain Entry
After entering the desired subdomain, the user clicks the Right (check) icon to proceed.
Confirmation Popup
A confirmation dialog appears informing the user that:
- Updating the subdomain will remove the currently acquired subdomain.
- The new custom subdomain will replace the existing one.
- The previous subdomain will be permanently released.
User Decision
If the user cancels, no changes are made and the current subdomain remains active.
If the user selects Update Subdomain, the update process begins.
Availability Check
Mayson verifies whether the chosen subdomain is available:
- If available, the system proceeds with acquiring and assigning the custom subdomain.
- If the subdomain is already taken or reserved by Mayson, an appropriate message is displayed below the input box.
Subdomain Assignment
After successful validation and confirmation, Mayson replaces the user’s current subdomain with the new custom subdomain mapped to .mayson.app.
Access the Application
Once the process completes successfully, the user can access their deployed application using the arrow button in the block through the newly assigned custom subdomain.