Everyone is aware that Samsung attempted to design its own operating system. Then there was “Bada,” followed by “Tizen.” However, all of these attempts might be regarded as failures in the end, which makes you wonder what the cause is. Google has maintained an open and flexible policy since the early days of the smartphone market’s inception, which were between 2008 and 2010, with no control over the operating system. This technique quickly drew device makers and app developers to the Android ecosystem. As a result, Google rapidly increased its market share, reaching 72% in the mobile OS market in just three years, in 2011.
Device makers were prohibited by the AFA from forking OSs themselves. Before getting into this, we need to know about Fork OS, which is an operating system (OS) that is adapted from the open-source Android source code (AOSP). The devices that are powered by the Fork OS are referred to as fork devices. An OS that fulfills Google’s compatibility criteria, as everyone knows, is Android, and devices are known as Android devices. Furthermore, Google outlawed the availability of SDKs for fork app creation, thereby blocking the establishment of a fork app ecosystem.
SDKs are toolkits required for app developers to construct apps that operate on certain operating systems and platforms. Google aggressively employed AFA to prevent device manufacturers from launching devices with a fork OS. As a result, mobile OS companies such as Amazon and Alibaba, which were unable to attract partners, eventually collapsed. Device makers were unable to release creative gadgets with new services. In 2013, Samsung Electronics attempted to offer a wristwatch with a forked OS.
Good Lock: Should It Be Integrated into One UI?
However, due to Google’s Anti-fragmentation Agreement (AFA), they were unable to incorporate the Play Store and Google applications on their modified device. This resulted in forced Tizen adoption by Samsung; however, it was unable to upset the established market, forcing them to migrate to the Android Wear OS. Good Lock cannot be incorporated into One UI for identical reasons. Google has been suspicious that Samsung may be adding additional functionality to One UI, perhaps making it into a forked OS, and has been hesitant to approve this. For a long time, Google actively opposed such initiatives. If the features of Good Lock are well received, Google has secretively borrowed them and added them to Android releases.
Because of Google, Samsung was unable to invest extensively in Good Lock in terms of both resources and manpower. For instance, One Hand Operation is a single developer’s software. This is just a disgusting action from Google. To conclude, Google is to blame for the inconvenience of having to download Good Lock only through the Galaxy Store, the separation of Good Lock from One UI, and the lack of availability of Good Lock in some locations.
Thanks to “Revegnus“
