Reusing App source and connected assets
New custom Apps are ordinary multi-file React programs. Reuse source modules and starter templates where they help, then adapt the App to its users. Shared storage and operational APIs remain independent of presentation. Questions, conditions and task sequence belong to App source and optional settings; they do not require a separate Form entity.
| Reusable piece | How it is used |
|---|---|
| App source/template | Copy or adapt ordinary React controls and task logic. |
| Table | Connect the same typed records to several authorized Apps. |
| Evidence | Share records through their authorized order, position or holder. |
| Automation | Connect a separate reusable process through a named manual action. |
| Document template | Select an appropriate report layout and published source binding. |
The Data entry starter demonstrates direct Table writes and resumable private drafts. The Production station starter demonstrates customer-order work. Both are editable source. A copied App is independent of its starter; later starter changes do not silently replace customer code.
Edit source or settings
Ask Konnie or an external agent to modify the existing App, or use its file editor. Preserve unrelated source and connections. Use normal App settings for selected customer-editable text and choices. Source changes compile and save as an App draft; publication is separate.
Programs execute in the isolated App runtime and call scoped APIs. They do not gain permissions by importing a library or drawing a control. Use named data sources and direct evidence/domain APIs rather than hidden native components for access. Existing component Apps can retain their supported native controls; the separate Form component is retired.
Verify and publish
Test loading, empty, error and narrow-screen states, keyboard/touch interaction, actual save status and submission recovery. Build feedback establishes compilation, not a successful operational action. Publish the reviewed App separately and test it with the intended account.
See Data entry in Apps, App data sources and Publishing and governance.