- Shipped
- September 24, 2026 at 8:21 AM UTC
- Author
- Kamo
- Commit
- 5b9e990
The mortgage application now lays itself out as the product was published (Settings → Features → CRM → Publish this application): - Type. NORMAL is the five grouped steps as before. SQUEEZE asks one question per screen: an eyebrow saying where you are, the question in the display face, a plain-language line on what it means and why it is asked, then one answer. Fields share a screen only when they are parts of one answer (a name, an address, an agent and their company). Tapping a choice moves on after a beat; the keyboard selects with arrows and moves on with Enter. The rail fills question by question. - Contact info. START asks who the borrower is first, and saves the lead the moment there is a name and an email — behind an invisible proof-of-work, the same the send button needs — then adds each later answer to that lead through a token, and the final send finishes it rather than filing a second. The page says so beside the contact questions. LAST moves contact to just before consent, and nothing is saved until the form is sent. - Fields. BASIC keeps name, email, phone, purpose, how the home will be used, state and ZIP, price or value, down payment or balance, and credit. Help text assumes the reader knows nothing: down payment, credit score, HOA, taxes, insurance, the loan programs and the property types are each explained where they are asked. Unanswered yes/no questions stay null (skipped or not yet reached) instead of arriving as "no". Also fixed, both live today: the consent paragraph never named the lender ("you give your express written consent to contact you" — a function passed as an ICU argument rendered nothing), and the receipt's "A copy is on its way to ." dropped the address the same way. The consent lead-in no longer starts with a lowercase "someone". Proxies: **************** (POST) and /progress/{token} (PUT), sharing the X-Forwarded-For handling with the submission. Needs securityservice d345869 for the layout and the progress endpoints; against an older backend the form is the grouped, full, contact-first form and the first early save 404s once and stops.