Transfer
Move this household's whole record to another phone: the saved horoscopes, the days you marked kept, the malas you counted, your notes, your tradition, your place and your reminder settings. One phone shows the code, the other reads it. The details pass between the two screens and nowhere else.
Send
Nothing saved on this device yet
Nothing is saved on this device yet. Save some birth details on the Porutham or Jathagam page, mark a day on the vratam tracker, and come back when there is a record to move.
Receive
Read the code shown on the other phone
This browser cannot read a code from the camera, so paste the code across or choose the file the other device saved.
Nothing is written until you have seen what the record holds and said so.
Read more Show less
A file that is damaged, or that did not finish downloading, is refused whole rather than applied by halves: half a record restored is worse than none.
Nothing leaves the two devices
The codes are drawn on this screen from what is already stored in this browser, and read by the other phone's camera.
Read more Show less
No server is involved at any step, so the whole transfer works with both phones offline, in a room with no signal. Nothing is uploaded, and nothing is kept anywhere but on the two devices.
What does not travel, and why
udaya-cart- The shop basket: slugs and quantities only. Prices and stock move, so a basket restored onto a new phone would show last month's, and a basket is a moment, not a record.
udaya-timeline-lanes- which extra lanes (Gowri, Choghadiya, horas) the panchang timeline shows: a view choice for this screen, not part of the record.
udaya-recent-tools- the last few tools opened on this phone, shown at the top of the More sheet: a per-device shortcut, not part of the record.
udaya-household-mirror- a copy of what other members shared, refetched the moment this device rejoins. Carrying a stale copy of somebody else’s records onto a second phone is the opposite of what the feature is for.
udaya-push- This device's own deviceId and secret with the alert server. They are credentials, not a record: two phones holding one identity means the server keeps one endpoint and the alerts land on whichever registered last, and the other phone could overwrite it. A secret shown on a screen as a QR code is a secret on a screen.
udaya-errors- The ring of the last fifty errors, with the page each happened on and the user agent. It is diagnostics about one device, it is the one key that can hold a fragment of anything that went wrong, and it is of no use on the new phone.
udaya-people-deleted- The tombstones: the people removed here and when. Carrying them would REMOVE people from the receiving phone whose records are older than the tombstone. A transfer must never delete somebody from the other phone, so the removals stay where they were made.
udaya-today-mark- A hint about what kind of day TODAY is on this device, with the date stored beside it. A date must never ride into a restore; it would be stale the moment it arrived.
udaya-state-v1- The contents of the porutham and jathagam forms as they were last left, which is a half-typed stranger's birth details rather than the family's record. It is also the one key state.svelte.js writes back from memory when a page is hidden, including the reload an import ends with, so a restored copy would be overwritten by whatever page happened to be open. Two reasons, either one sufficient.
udaya-welcomed- Whether this device has seen the welcome. The new phone has not.
udaya-install-dismissed- Whether this device dismissed the Add to Home Screen prompt. Carrying it would hide that prompt on the one phone that has not been asked yet, and on iOS the Home Screen is what notifications depend on.
udaya-reminders-updated- The change stamp for the reminder settings. It is set to the moment of the import instead of being carried, so a restore is never undone by an older copy on the server.
Everything else this app stores for your household is carried, and the record names every part it holds so that a part which went missing on the way is noticed rather than lost.