The fruit that’s offered in the supermarket is unripe but it’s ready to be consumed a few days after it’s been bought. This is due to long transport routes - bananas, for example, are harvested and delivered when they’re green and they only acquire their sweet aroma after they ripen. Is there anyone that doesn’t already know this?
Unfortunately, a similar procedure is being observed more and more when it comes to technically complex products: they’re brought to the market prematurely and therefore, they’re full of bugs. They only become fully functional later on via software updates or device revisions. This creates frustration, and rightfully so. In Germany this has led to the sarcastic expression, "the banana principle" (editor’s note: “perpetual beta”).
We think that customers should only accept testing solutions that have had time to mature. But what does that mean? Are continuous product care and necessary improvements the same? No, because it is important to distinguish whether
1. a functioning product is further improved via updates, e.g. the range of functions is expanded, or
2. a product was brought to market unfinished and buggy and therefore needs to be repaired.
The first case is desirable but the second one should be avoided. The best-case-scenario is having a product that functions smoothly from the very beginning and is maintained over a long period of time – only then can it really be referred to as "mature". The path that leads to this goal is not always easy, but it’s a challenge that we’re prepared for.