Documentation/Commerce user guides

Mobile App Studio

Design, validate and publish supported iOS and Android app experiences.

On this page

Enter the mobile workspace

App Studio is a separate workspace at apps.rocento.com. Sign in there and select a merchant you are a member of. Core Admin access alone does not grant mobile membership.

The builder edits Production drafts. Catalog, orders and customer operations remain in their existing commerce workspaces.

RoleStudio actions
OwnerPreview, edit, validate, publish and roll back.
DesignerPreview, edit and validate.
OperatorInspect the experience and history.
Release adminInspect Studio; separate backend build-queue permissions do not grant publication.

Compose the app experience

Presets append sections instead of replacing existing content. Add your own artwork and catalog selections. The current contract allows up to 30 sections and only registered native components.

  1. Set the in-app name and logo, light/dark colors, radius and density.
  2. Use the component library and presets to arrange supported home sections. Drag sections or use the accessible move buttons.
  3. Configure category/product destinations, banner actions and tab order.
  4. Review English and Arabic copy, including right-to-left layout.
  5. Preview iOS and Android at compact and large widths in light and dark modes.

Save and validate the draft

Valid edits autosave. Invalid input pauses saving. A conflicting revision preserves your local edits so you can download them or explicitly discard and reload.

Validate draft runs server checks for the schema, color contrast, translations, asset ownership, entitlements and compatibility. Resolve failures before requesting owner review.

Review and publish

  1. Verify the intended experience in both real native applications, not only the browser previews.
  2. As an owner, inspect the release diff and approve the current review.
  3. Publish the validated Production draft.
  4. Confirm the new version in release history and verify the native experience.
  5. For recovery, choose a previous version and review an owner-approved rollback; rollback creates a new version.

Know when a new app build is needed

Studio publication is not an App Store or Google Play submission. Available native features depend on the installed runtime and merchant entitlements.

ChangeRelease path
Supported theme, in-app copy and layoutPublish a compatible configuration release.
Launcher icon, splash, native identifiers or store listingSeparate app build and store-release process.
New native components or device capabilitiesRuntime implementation and device validation before configuration support.