Skip to content

Save places in the app - #64

Merged
octopranav merged 1 commit into
mainfrom
android-saved-places
Sep 24, 2026
Merged

octopranav merged 1 commit into
mainfrom
android-saved-places

Conversation

@octopranav

Copy link
Copy Markdown
Owner

What

Saved places, the R1 scope you settled: kept on the device, no contacts, no print, no export.

  • Save. The bookmark on a place's card opens a small dialog: a name ("Home, the clinic's side door") and the directions to the door, both optional. The card then shows the place's name, however it is reached: the list, a search, a link or a tap on the map.
  • One place per code. Saving a code that is already saved changes it rather than listing it twice. Removing is in the same dialog, where it is a deliberate choice rather than a slip of the thumb.
  • Open. A bookmark button on the map lists every saved place, newest first. Opening one goes there with its own directions, which come back into the address and its link.
  • Search. As anything is typed, saved places whose name or directions hold it come first, instantly and with no connection. Matching folds accents and case, so cafe finds "Café Rosa". Go on a saved place's whole name goes straight to it.
  • Map. Saved places are drawn as small rings under the drawing: context for the place on screen, never mistaken for it.

Where they are kept

One small JSON file in the app's own files, which the device's backup includes, so a new phone has them. It is written whole to a file beside it and moved into place, so a crash halfway through cannot leave half a list. Writes run one at a time, in order. There is no account to sync to and no export, by the decision the website made when it took its export down. Syncing to the watch comes with Wear OS in R2.

Checks

  • SavedTest (7 tests):
    • newest first and one place per code
    • names kept tidy and at most 60 characters
    • forgetting only the place asked for
    • finding by any word of the name or the directions, without accents
    • Go only on a whole name
    • opening restores that place's directions and stops listening for a fix
    • a saved code that will not read leaves the place where it was
  • 98 core tests pass.
  • On the emulator:
    • Saved the example point as "Office" with "Side door on Adelaide". The card showed the name, and the file held both.
    • From a London code, the list and Go on office each went back, labelled "A saved place", with the directions in the address and in the link (&n=Side+door+on+Adelaide).
    • Typing off listed Office first.
    • After a force stop, the card still named it.
    • A place saved one cell west showed as a ring beside the current cell.
    • Remove emptied the file and returned the card to "Save this place".

The bookmark on a place's card saves it with a name and the directions to
its door. Saved places are listed from a button on the map, drawn on it as
small rings under the drawing, and found first as anything is typed, with
no connection. Opening one goes there with its own directions, and Go on a
saved place's whole name goes straight to it. The card shows a saved
place's name however it was reached. Saving a code again changes it rather
than listing it twice, and removing it is in the same dialog, where it is a
deliberate choice.

They are kept in one small file in the app's own files, which the device's
backup includes, written whole and moved into place so a crash cannot leave
half a list. No account and no export, by the decision the website made.
@octopranav
octopranav merged commit 4d242f1 into main Sep 24, 2026
21 checks passed
@octopranav
octopranav deleted the android-saved-places branch September 24, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant