Feature flags: when the feature exists, but kind of doesn’t
In PDP and PDP Mobile, external integrations and features are controlled through feature flags: CRM, payments, and access control can be enabled selectively, all the way down to a specific building.
In PDP and PDP Mobile, we manage external integrations and feature availability through feature flags. CRM, payments, access control — everything can be turned on and off selectively, all the way down to the level of a specific building.
A real-world case: we launch a new residential complex, but the access control system hasn’t been installed there yet. Without flags, this would be the classic “oops, we shipped to production and the button doesn’t work.” With flags, we just disable the access control block and carry on спокойно.
But there’s a catch, and it’s one of those “small setting, big consequences” things: every new flag increases the combinatorics. 10 flags already gives you 1024 combinations. Testing everything manually isn’t QA — it’s survival mode.
What we do is not try to test absolutely everything, but focus on critical paths. That kind of pragmatic engineering is especially relevant now, when everyone wants to ship faster, but without surprises in production.