A user can add an expense through the mobile client and later review it on nesthome.zactra.com when both clients point to the same live backend and account.

Put this into practice

Apply the guide first with one real record or a small test category, then confirm that totals, dates, permissions, and reports look correct before entering a larger history. Keep exports securely, use descriptive names, and give family access only to people who genuinely need the shared information.

• Start with sign in through the approved client and write down the result.
• Verify confirm family and currency context and write down the result.
• Review save before switching devices and write down the result.

What to measure

• Record count: write down the confirmed value and the source used.
• Date range: write down the confirmed value and the source used.
• Selected category: write down the confirmed value and the source used.
• Currency and permissions: write down the confirmed value and the source used.
• Result after saving: write down the confirmed value and the source used.

Use the same definitions throughout the review period. A total is only useful when every person records the same type of event in the same way. Keep source records long enough to correct mistakes, but do not collect private information that is unrelated to the household decision.

Your first checkpoint

At the first checkpoint, reload the application and confirm the saved record appears in the correct screen, report, family scope, and currency. Fix a test record before entering a large history, and keep private exports or images secure.

Write one sentence explaining what changed, why it changed, and what the household will do next. This keeps the review focused on a practical decision instead of producing reports that nobody uses.

Common mistakes to avoid

• Creating duplicate records after switching devices before the first save completes.
• Pointing the mobile build at localhost or an obsolete API base URL.
• Sharing one account password instead of inviting separate family members.

How NestHome can help

The public API route structure remains unchanged. The reverse-proxy security layer recognizes nesthome.zactra.com, expense.zactra.com, and configured native origins while continuing to reject untrusted cross-site mutations.

Questions people ask

Can the mobile app still call expense.zactra.com?

Yes, when that domain continues to proxy to the same service and the mobile build uses its HTTPS API base URL. Existing API route paths are preserved.

Why might login work on one domain but not another?

Sessions, cookie handling, forwarded headers, CORS, and the client’s API base URL must all match the deployment. Test login and an authenticated read on the exact domain used by the client.

This article is general educational information, not personal financial, legal, tax, or investment advice. Adapt every example to your own income, obligations, location, and risk.

Published by NestHome Editorial Team. Content license: All rights reserved. Last reviewed August 6, 2026.