White-label Flutter SDKs That Actually Scale Partners

At RentOk I worked on Flutter SaaS used by tens of thousands of property owners and hundreds of thousands of tenants. The enterprise twist was white-label: partners wanted branded tenant apps without waiting for a full custom build every time.

The SDK bet

We packaged shared product modules behind a Tenant App SDK — configuration-driven flows, reusable mobile modules, and partner-specific branding. That approach contributed to roughly 80% enterprise revenue growth because partners could ship faster without forking the entire codebase.

Dynamic branding

Branding isn’t just a color token. Partners needed runtime logo/icon switching and Android-specific app identity handling. The dynamic branding library made identity a platform concern instead of a permanent fork tax.

What I learned

White-label succeeds when the shared core is boring and reliable, and the extension points are explicit. If everything is configurable, nothing is. If nothing is configurable, every partner becomes a special case. The SDK lived in the middle — opinionated product, flexible identity.

Promotion as a signal

I joined as SDE-1 and was promoted to SDE-2 while owning iOS delivery, SDK work, and cross-platform feature leadership. The lesson for me: ownership of multi-app delivery compounds faster than isolated feature tickets.