Skip to main content

After launch: active and parked apps

After launch: active and parked apps

While a client app is in active development, it follows VWL: new features and fixes arrive with every update.

When active development ends, the app is parked. It gets its own copy of the VWL code base and stays on a fixed version of the shared business modules. It keeps working as released while the base product moves on, and it can still be fixed and changed at any time.

The lifecycle

Stage What happens
Active development     The app follows VWL. Everything below the client layer is shared
Release The app is published in the store
Parked The app layer becomes the app's own code base; the modules stay at a fixed version
Return The shared modules are updated to the current version, bringing new features and improvements

What parking means for the client

Parked does not mean frozen or unsupported. It only means the app no longer follows VWL automatically.

  • Fixes arrive as fast as before. Bugs and urgent issues are fixed directly in the app's own code base and released in the usual way.
  • The app can still be changed. Texts, colours, rules, documents and feature switches are changed directly in the app's own code base. Documents and terms can change even without a new app version.
  • A return is only for new VWL features. When the client wants something added to VWL after parking, the modules are updated and the app is adjusted where needed.
Advantages and trade-offs

Advantages
  • Stability – the app changes only when the client asks, so its behaviour stays as tested and accepted.
  • Lower maintenance cost – no continuous alignment with VWL and no repeated regression testing.
  • No accidental regressions – changes made for other clients cannot affect this app.
  • Predictability – it is always clear which version runs in production.
Trade-offs
  • Catch-up cost – the longer the app is parked, the bigger the module update on return.
  • No automatic new features – VWL improvements arrive only after the catch-up.
  • External deadlines – store requirements, new OS versions or security updates can force an update even while parked.