Launch on one platform first to validate" is bad advice if your product is two-sided. What it cost me.

The standard advice for a solo builder is to ship on one platform first, keep it cheap, validate, then expand. I followed it and it backfired, and the reason is worth sharing because it applies to anyone building something with two sides (marketplace, B2B2C, anything where the person who pays isn't the only one who has to show up).

I'm building a tool for small landlords who rent out rooms to students. Two sides: the landlord, who pays, and their tenants, who use it for free. I shipped Android only, telling myself it was enough to test demand.

Here's the trap. In a two-sided product you don't control which platform the second side is on. The landlord might be on Android, but their four tenants own whatever they happen to own, and half are on iPhone. The moment one tenant couldn't join, the landlord's experience broke too. So "one platform" didn't give me a smaller working product, it gave me a non-functional one for anyone whose group was mixed, which is basically everyone. Single-player apps can validate on one platform. Multiplayer ones can't. The network is the product.

What I'd do instead, and eventually did: find the smallest unit that has to fully work for ONE customer to get value, and cover all of it, even if that's more surface area up front. For me that meant iOS and Android together, then a web version on top, because the easiest way to get anyone to even try turned out to be a link with nothing to install. The thing I'd filed under "phase 2" was actually part of phase 1.

Learning this the slow way cost me a couple of months and a pile of wrong assumptions I could've skipped by asking one question first: does my product deliver value if only one side shows up? If the answer is no, "validate on one platform" isn't written for you.

Genuinely curious if anyone here has shipped a two-sided or multiplayer micro SaaS and found a cheap way to validate it, because I'm not convinced one exists. The whole "start tiny" playbook seems written for single-player tools.

(The product, for context: https://plinthos.app)