AppSwift
AppSwift builds working apps from your Archivo files. You design an app once, in an .aps file in My Documents. You publish it to a workspace, and the people there run it from its tile.
One design, many installs
Section titled “One design, many installs”An install is one live copy of your app in one workspace. You can publish the same design to many workspaces, or more than once to one workspace. For example, one attendance app can run for HR, for Sales and for the field team.
| Each install keeps its own | Every install shares |
|---|---|
| Data (records, rows and files) | The screens and the layout |
| Rules and their run history | The design of each rule |
| Tile and name | Design updates you publish |
| Share list and public link | |
| Version |
An install never reads another install’s lists or folders. A rule in one install runs on that install’s data only. Two installs in one workspace can use the same single file, such as one rates workbook. Install here tells you when it does this.
Installing in another workspace
Section titled “Installing in another workspace”Open the .aps file while you are in a different workspace. AppSwift finds the installs that already exist. It does not make a duplicate by mistake.
- Install here makes a new install in the workspace you are in. Give it a name, such as “Field team”.
- Install here makes new, empty lists and folders for the install, with the same columns. It copies the rules too, but each copy starts switched off. Check each rule, then switch it on.
- Set up appears when you add a list or folder to the design after an install exists. It makes that install’s own empty copy. Until then, that install is held back from updates.
Publishing an update
Section titled “Publishing an update”Publish opens a checklist with one row for each install you can reach.
- A row says which version the install runs, and whether it is behind.
- Tick the installs to update. Each one gets the new design and keeps its own data.
- A row that cannot be published says why, such as a missing Set up. The other rows still publish.
- Required is chosen per install. People in that install must take the update.
- Roll back returns one install to an earlier version. The other installs stay where they are.
Unpublishing one install
Section titled “Unpublishing one install”Unpublish removes one install only. You pick which one. The other installs keep running, with their data.
Asking Archivo Pilot
Section titled “Asking Archivo Pilot”Archivo Pilot can publish for you. Name the installs in plain words, for example “publish this to HR and the field team”, or “publish to all installs”.
- Pilot lists the installs, their versions, and which ones are behind.
- Pilot always asks you to confirm before it publishes.
- If a name could mean two installs, Pilot asks which one. It never guesses.
- Pilot unpublishes or rolls back only the install open in the builder.