Edit and Improve an Existing App

When to use Forge for changes

Use Forge when you want your existing App to work better for real life—like making it simpler, adding a checkbox, reorganizing the screen, or changing default options. You’ll describe what you want in plain language, and Forge updates your App.

Open Forge from an App

Go to your App Library, then open (run) the App that needs an update. In the App, open the menu (often in the top corner) and choose Forge, Edit in Forge, or Request changes. Forge will show the App name and your recent conversation about it. If the name doesn’t match, go back and open the correct App first. If you don’t see a Forge option inside the App, you can also open Forge from the main Spanner screen, then select the App you want to edit from your App Library.

Ask for changes (what to say)

The most helpful requests are specific and describe what you want to be different when you use the App—not technical details. Think in terms of: what you do, what you want to see, and what should happen by default.

A simple template you can copy

In this App, I want to change:
1) What I enter: 
2) What I see on the main screen:
3) Defaults (what should be pre-filled or selected):
4) Anything to remove or simplify:
Include one real example. For example: “When I add an item called ‘Milk’, I want the quantity to default to 1 and the ‘Purchased’ box unchecked.”

Common change requests (with ready-to-use examples)

Example request:

Make this App simpler for quick use.
- Remove any fields I don’t need every time.
- Keep only: Name, Notes, and a Purchased checkbox.
- On the main screen, show a simple list with Purchased items dimmed.

Good to mention: which fields you never use, and what you want the “main screen” to look like.

Example request:

Add a checkbox called “Done”.
- Default: unchecked
- When I check it, the item should move to the bottom of the list.
- I still want to be able to uncheck it to bring it back.

Good to mention: the name of the checkbox, the default state, and what you want to happen when it’s checked.

Example request:

Reorganize the entry screen so it’s faster.
- Put “Title” at the top.
- Put “Category” right under Title.
- Move “Notes” to the bottom.
- Keep the Save button easy to reach.

Good to mention: which screen feels messy (main list, add/edit screen, details screen) and the order you prefer.

Example request:

Change the defaults:
- Default priority should be “Normal”.
- Default due date should be blank (not today).
- Default category should be “Home”.

Good to mention: what the current default is (if you know it) and what you want instead.

Example request:

Rename a few labels so they make sense to me:
- Change “Entry” to “Item”
- Change “Status” to “Purchased”
- Change “Description” to “Notes”

Good to mention: the exact words you want to see in the App.

Review the change before you rely on it

After Forge updates your App, open the App and do a quick “real-life” check:

  • Add one or two sample entries you would normally use.
  • Confirm the layout feels right (especially the main screen and the add/edit screen).
  • Confirm defaults are correct (checkboxes, categories, dates, etc.).
If something looks worse or confusing after an update, don’t keep fighting it—go back to Forge and say exactly what changed and what you want instead (for example: “Undo the layout change and keep the old screen order, but still add the checkbox.”).

Troubles you can solve quickly in Forge

Tell Forge what to keep and what to change, in one message:

Keep the current list layout exactly as it is.
Only add a checkbox called “Packed” to each item.
Default: unchecked.

Ask for a “minimum version” and name the must-haves:

Please simplify this App.
Must-have: add items, mark them done, and a notes field.
Remove anything else.
Main screen should be a clean list.

Be explicit about each default you want:

Set these defaults:
- Checkbox “Purchased”: unchecked
- Quantity: 1
- Category: Groceries
And do not auto-fill the date.

What happens to your App when you request changes

When you ask Forge for changes, your App is updated so the next time you run it, you’ll see the new version.

Spanner keeps a history of your App changes, so you can go back to an earlier version if a change doesn’t work out.