Skip to content
Docs

Start here

↑ ↓ navigate · Enter open · Esc closeSearch all 418 articles

Import a portable app

Review requirements, prepare connections, and create or update an app from a portable file.

Use Import app to bring a .strive.html package into your account. Import checks the file, the destination, resource access, and runtime compatibility before applying it. The app file limit is 16 MiB.

Review before importing

  1. Open Import app from Apps.
  2. Choose the app file. The dialog accepts portable HTML and its JSON package representation.
  3. Select Create new app or Update existing app UI.
  4. Review Name and App address.
  5. Fill in the package's parameter fields. Object and array fields require valid JSON of the indicated type.
  6. Select an active compatible connection for each connection requirement, or choose to prepare a new connection for setup.
  7. Choose Review and read every diagnostic and requirement.

A file can be structurally valid and still need connection setup or a more capable renderer. Ready to import confirms destination readiness; Review the requirements below means further setup is needed.

Create a new app

Choose Import app when the reviewed plan is ready. If it offers Prepare connections, proceed to create the setup resources, open Connections, finish authorization, and review/retry the import. Strive can retain generated setup bindings so retrying continues the operation instead of duplicating its resources.

The imported app has independent provisioned resources. Table schemas create empty app tables; the file does not restore the source app's live rows or credentials.

Update an existing app's interface

Choose Update existing app UI only for a compatible interface update. Existing workflows and data remain in place; unchanged table schemas remain bound to the same tables. A changed backend recipe or table schema requires creating a new app. Strive checks the current definition version and refuses stale updates rather than overwriting another writer.

Retry or correct

For an uncertain or transient failure, Retry import continues the same operation. Changing the file, destination, or user-entered values requires a new review and operation. A non-retryable workflow rejection shows the reason and jobs to change, and withholds Retry: correct the package first.

If an import needs attention, finish the requested connection setup. If validation fails, correct the named field or requirement and review again. Download authoring toolkit is available for advanced package authors; ordinary import does not require the toolkit.