Signed-in users see tabs based on their access role. Use Help on each card for page-specific guidance.
QA mode: you can test scoring and import workflow, but cloud saves are disabled.
QA Tester ā read-only cloud access. Save, delete, import/replace, clear, restore, and shared-criteria cloud writes are hidden or blocked.
Dashboard
Tracked homesLoadingā¦
Cloud statusLoading shared dataā¦
Current roleChecking accessā¦
Next actionOpen Ranked Homes or Property Entry.
Score Output
0.0/10
Enter or select a property
Select a tracked property or enter a property to calculate.
Est. payment
$0
Loan amount
$0
Payment gap
$0
Price / sqft
$0
Score breakdown
Estimated monthly payment breakdown
| Principal & Interest | $0 |
| Property Tax | $0 |
| Home Insurance | $0 |
| HOA | $0 |
| CDD | $0 |
| Total Estimated Monthly Payment | $0 |
| Estimated Annual Property Tax | $0 |
| Veteran % Discount Credit | $0 |
| Tax Basis / Model | ā |
Listing Import
Extracted preview
No listing text extracted yet.
After extraction, likely facts will appear here for review.
Property Entry
No photo yet
Optional: upload a real photo when the listing image is generic. Uploaded photo overrides the URL preview.
Buyer Criteria & Tax Assumptions
Preference Weights
Shared criteria sync
Criteria local/default
Shared criteria has not loaded yet.
Ranked Homes
| Rank | Score | Property | Listing / Features | Offer & Loan | Monthly Breakdown | Status | Actions |
|---|
Realtor Showing Export 0 selected
Include in export
Showing request note
| Send | Rank | Property | Score | Price | Tour details | Notes for realtor |
|---|
Saved Property Data
V13H can use Firebase cloud sync after sign-in, while still preserving the original browser/local JSON workflow. Use these controls to export an updated active JSON file, merge an imported file, or replace the active cloud/local list from a JSON backup without accidentally wiping viewed/drive-by tracking.
Import modes: Merge/update keeps the current list and adds/updates matching records. Replace active list exactly makes the saved/cloud list match the imported JSON and clears the hidden/removed list, which is the correct restore behavior when you want to go from an older 33-record backup back to a newer 22-record backup. Viewed/drive-by handling defaults to preserving current live tracking so an older JSON file cannot reset homes you already marked as viewed or drive-by.
Browser-saved entries you can delete
Deleting here removes the browser-saved copy. To remove any property from ranked tracked properties and the exported active JSON, use the red āRemoveā button in the ranked table.
| Saved Address / Plan | Offer | Link | Favored | Viewed | Drive-by | Action |
|---|
Removed / hidden properties
These are excluded from rankings and from the active JSON export. Restore them here if you change your mind.
AI Decision Advisor
V16C production mode: this screen packages finalist homes, tie-breakers, and score data, then calls a secure Firebase Cloud Function. The OpenAI API key stays server-side in the function and is never stored inside this HTML file.
Buyer-side goal
Help Ray and Ana compare the final favorite homes using both the HomeTracker score and real-life tie-breakers that matter when living with the purchase for the life of the loan.
Best overall fit
Best value
Lifestyle fit
Risk flags
Tie-breakers
Realtor questions
Advisor input controls
Example tie-breakers to capture
Choose a dropdown value, or choose Other / custom to type your own buyer-specific priority. These are true dropdowns now, so you can reopen and change a choice without first deleting the old value.
Ready. Deploy the Cloud Function, then run a test against selected finalists.
Security plan: the browser calls Firebase only. The Cloud Function validates signed-in user access, checks the HomeTracker role, and calls the AI service server-side. No OpenAI key is stored in the public GitHub Pages file.
1. Pick finalistsUse favored homes first, favored-only, or top-ranked homes as the input set.
2. Package safe dataSend only property facts, score breakdowns, buyer notes, and verify-before-offer notes. Avoid unnecessary personal or financial details.
3. Run Cloud FunctionThe callable function validates auth and role, then returns structured decision-support output.
4. Keep human controlThe output is decision support only. Buyer, realtor, lender, tax, HOA/CDD, insurance, and inspection details still need verification.
Payload preview
Use the PDF report button after a Cloud Function result appears. Your browser will open a clean buyer report that can be printed or saved as PDF. Watch-item wording now separates true missing verification gaps from normal buyer due diligence and feature/cost tradeoffs.
No AI Advisor report yet.
HomeTracker V16C: login-first access, role-based tab visibility, QA Tester read-only cloud UI, self-service password reset before sign-in, cleaner header layout, responsive buyer/realtor image, AI Advisor production workflow, page-specific help, a one-hour inactivity sign-out timer, Firebase App Check monitoring support, and Node.js 22 Cloud Function runtime cleanup.
Roadmap: deploy/test the AI Advisor Cloud Function, add structured recommendation output, add optional saved AI reports, realtor read-only access, tighter admin tools, API/MLS automation planning, map/comparable sales views, and lender-specific assumptions.
Dashboard: shows the signed-in user, role, tracked-home count, and quick status. Admin sees the most tools; user and realtor views are limited by role.
Score Output: shows the current propertyās weighted score, estimated payment, loan amount, payment gap, price per square foot, score breakdown, and monthly payment model.
Listing Import: paste a listing URL and copied listing facts. The extractor fills likely fields, but HOA, CDD, fence, baths, and lot/view details still need human review.
Property Entry: add or update a home, photo URL, favored flag, viewed/drive-by status, numbers, yes/no fields, notes, and verification items. Click Save/update to sync changes.
Buyer Criteria: controls payment target, loan cap, down payment, rate, term, insurance, tax model, exemptions, and minimum bed/bath assumptions.
Preference Weights: check the features that matter and keep active weights at exactly 100. Save shared criteria after changes so Ray/Ana devices use the same assumptions.
Ranked Homes: compares active homes using the current criteria. Admin/user roles can update flags and load/edit. Realtor role is limited to viewing and export workflow.
Realtor Export: select homes for Julius or another realtor, choose export fields, and create a CSV or print/PDF showing request.
Saved Data: admin maintenance area for JSON backup/restore, merge/replace behavior, hidden homes, and manual saved entries. Leave this alone unless intentionally managing backups.
Access setup: create the Firebase Auth user, add the user to the household members collection with the desired role, then sign in. Roles for V16C are admin, user/editor, qa, and realtor. QA is āQA Tester ā read-only cloud accessā for safe import/scoring/display testing without cloud writes. Users can also request their own password reset email from the login screen or signed-in session bar.
Session timeout: V15B signs users out after 60 minutes with no activity inside HomeTracker. A five-minute warning appears at 55 minutes. Activity on outside listing sites does not reset the HomeTracker timer, so one hour was chosen to reduce inconvenience while researching homes.
Password reset: users can request a Firebase password reset email from the login screen by entering their email and clicking Forgot / reset password. Resetting an existing user password does not change that userās Firebase UID.
AI Advisor: V16C packages selected finalist homes and tie-breaker priorities, previews the payload, and calls a secure Firebase Cloud Function. The function should validate signed-in access and role before returning buyer-side decision support. Tie-breaker fields use dropdown suggestions, but users can type a custom item when the list does not cover what matters. The output can be opened as a clean print/PDF buyer report.
MLS/API planning: capture API provider, authentication method, allowed data fields, image/media access, usage limits, caching rules, attribution requirements, and whether a backend/proxy is required.