Release Notes

Clicking a property card from the search dropdown was showing 'Something went wrong.' Refreshing showed the correct page. The property page loader was using a server-only Supabase client — fine for a direct URL load, broken for in-app navigation where the loader runs in the browser. Fixed: anon client, which works in both contexts. Property data is public anyway.

Sign-in and sign-up analytics were flat-zero across the board. Newer Supabase only fires the SIGNED_IN event when a user explicitly authenticates — not on page load. Most users sign in once and run on auto-refreshed sessions indefinitely, so almost nobody was triggering it. Fixed: now also tracks session starts, once per browser session. Also added console logging to track insert failures, since analytics errors were silently disappearing.

Someone posted Inkwise on r/SingaporeRaw and a commenter audited the client-side bundle. They flagged stored XSS, reflected XSS, and SSRF. None of those were real — React escapes all text by default, and every outbound API call uses hardcoded government URLs with encoded query strings. But 'not real' isn't the same as 'nothing to look at.'

Designated a Data Protection Officer as required under Singapore's PDPA. DPO contact (dpo@inkwise.club) now in the privacy policy header and in its own section. Should have been there from day one. It wasn't.

Five new guides: end-of-tenancy checklist, fair wear and tear (and how landlords misuse it), what happens when your landlord wants to sell mid-lease, renewing vs. moving with actual break-even math, and what to do when your landlord refuses to return your deposit. The deposit one in particular was overdue.

Property pages were being indexed by Google as 'inkwise.club' with no other context. Every property page now has a proper title and description — address, building name, Singapore postal code — so searches for an actual building lead somewhere useful. Took three weeks to notice.

Blog posts were not in the sitemap. Search engines had no way to find them. Added. Also removed /me/reviews and /admin/login from the sitemap — they require a login and have no business being indexed.

The admin Rejected tab was crashing with 'Something went wrong' every single time. When an admin manually rejects a review, it writes a value that wasn't registered anywhere in the display layer. The tab tried to read a label from it and threw. Every manually rejected review was invisible until a hard refresh. Claude didn't catch this. A real user did. Fixed.

Tenants were getting 'Please select tenancy start and end month/year' on submit even though the date dropdowns looked filled. The picker was updating its own display but quietly forgetting to tell the form. Claude couldn't find the root cause. Lovable did. We've noted this for future reference. Fixed: the picker now reliably tells the form what it knows, regardless of how many times you change your mind.

Blog live at /blog. First piece: 7 questions to ask before renting a condo in Singapore — the ones tenants don't think to ask in the 30-minute viewing but wish they had six months in. Also: stamp duty (most tenants don't know they're liable) and agent commissions post-2024 CEA guidelines.

Homepage roadmap added — what's coming next, honestly, so tenants don't go looking for features that don't exist yet.

Step 3 was showing 'Tenant Verified,' 'Lease uploaded,' and 'Review will publish immediately' after a failed document extraction. All three wrong. The review was heading to moderation. Fixed: failed document = same copy as no document. Because they're the same situation.

Clicking a property from search was sometimes landing back on the search results page — the one you just clicked from. The loop was not a feature. Fixed by matching on postal code, which uniquely identifies a building in Singapore.

Error messages across every form had been showing raw developer shorthand since launch. The kind of thing nobody fixes until a real user screenshots it. All rewritten in plain English.

Tried to make unit number mandatory at Step 1. Properties don't always have one yet at that point. Reverted. Fixed the edge case. Tried again. Reverted again. It's optional at Step 1 and required at Step 2. Twice the work, same answer.

Four fixes shipped in one sitting. None glamorous. All of them quietly ruining someone's day.

The email system had been silently failing since launch. Every signup confirmation, every review notification — going nowhere. It was pointed at an old staging URL that had quietly expired. We were watching a full send log of 'delivered' for emails that vanished. Fixed: it now points at inkwise.club. Lesson: check the URL before celebrating the infrastructure.

First real users. First real bugs. Fixed live without looking panicked (barely).

The original review flow was held together with vibes. Rebuilt as three proper steps: write your review → upload your lease → confirm what was extracted. Much harder to abandon halfway.

Built the email system — queues, retry logic, failure handling, send logs. The kind of plumbing nobody celebrates until it breaks and everything burns. (Foreshadowing.)

Feedback widget added so early users could tell us what hurt. They did. Analytics added so we could see what people actually did versus what we assumed. Very humbling.

Two days of fixes nobody asks for and everybody needs.

'4 stars' tells you nothing. Rebuilt with 7 rating dimensions: Responsiveness, Deposit Fairness, Repairs & Maintenance, Entry Notice, Listing Accuracy, Building Condition, and Facilities. Pros and cons bullets added — three sentences that tell you more than any star rating ever could.

This update wiped all existing test data. The schema needed it. Worth it. Probably.

The first audit missed 8 more things. Classic. Fixed those — content safety, admin access, the basics. Lesson: audits are just bugs with better PR.

Privacy policy written by a human, not copy-pasted from a 2014 legal blog. Singapore skyline on the homepage — before this, it was giving government portal energy. This is the version we could actually tell people about.

Full security sweep before launch. Found 14 things wrong — broken auth, security gaps, design choices that aged poorly overnight. Fixed all 14. Celebrated for four minutes.

Upgraded to a smarter AI model. Also had to document that the AI needs an API key to function. Yes, that needed to be written down.

Blank page to working product in one day. Could've rested. Did not.

Search any Singapore address, read real tenant reviews. AI reads your lease so you don't have to. Rents cross-checked against official data — because 'great deal' is landlord for 'something is broken.'

Dark teal design because beige is for landlords. Was it held together with hope and auto-saves? A little. Did it work? Yes.