5 apartments, 1 user, 0 pain: how we built multi-object support in PDP Mobile

We ran into a very real-world problem: a user doesn’t have just one apartment, but five — in different residential complexes. And at that point the home screen starts behaving like a group chat after a release: everything matters, but what should come first?

We solved this with an object context switcher: the user switches between apartments, and the app preserves the history, settings, and state for each one. So when they return to an object, everything is still there — no “wait, where was I?” moment.

An extra challenge was notifications for an inactive apartment. We handle those correctly too: a push notification takes the user to the right object instead of dumping them into UX chaos.

And yes, price lists are tied to buildings: different residential complexes have different services and rates. That means the object context affects not just the UI, but the business logic as well.

Against the backdrop of the broader move toward hyper-personalization in products, this is no longer a feature — it’s a must-have. We made sure multi-object support doesn’t break the experience for either the user or the system 😌