Herald – Bluetooth contact tracing protocol

These apps need to use the OS APIs, otherwise there is no hope for them. The German app uses those APIs, the Australian one does not. While there are obviously trade-offs involved with the OS APIs, it's not hopeless like this clusterfuck.

Since it is open source and uses a very common tech stack, it is easy to check and understand for as many people as possible that it is well-crafted and does not contain any obvious security vulnerabilities or backdoors. This makes it very trustworthy from an IT-persons point of view, and should in minimize the number of unsettled people who don't install the application on their handsets since they mistrust the government.

Well-known public instances like the CCC (German IT-Security NGO) did a review on the app and gave it a good testimonial - even on mass media like public television. The government and the involved third-parties like Deutsche Telekom and SAP did a lot to emphasize that there is no harm to be expected from the app and the worst thing that could happen is that it doesn't work - which would be the exact same outcome as if you just didn't use it.

Still, Germans' are hard to convince, once they made up their mind about something. The public image of the government, as well as Deutsche Telekom and SAP is often disconnected from their actual performance. The same people often disregard these instances' and companies' ideas, products and services with the same persistence they welcome or defend equaly debatable innovations and decisions from actors they look favorably upon, like Apple.

It's sad to see that the good work of many smart people is so easily disregarded. The government and the involved companies actually listened to privacy and security experts and made a lot of right choices. That's something I'd like to see more of in the future. A little bit of appreciation could go a long way for shaping such decisions for the years to come.

This is the core reason I'm so against these duopolies. I have a startup idea that I want to implement. I've done it on windows, and it's flawless. Should work on macOS too. But these mobile OS's don't provide the right API's to do it. Android offers access to do it in a half assed way, and the way to do it right is to do it the correct way, flawlessly. So I'm stuck in a limbo, I want to be the first and last to market, prepared for when these companies break up, the OS offers access to some API's I want, and capture the market. There may be little network effects to the idea. But it's going to be a big market for everyone, with plenty of competition if idiots offer the right API's. [edited it gave away a bit too revealing info]. Enough that I don't ever connect my development machine to the internet to make sure no source code ever leaves.

My test users have asked me when will I offer a mobile app? The app needs mobile integration to make it work the way the idea was supposed to be. All OS's that the user uses, together.

And, I have no response to their questions and the mails end up collecting dust.

These fuckers ruin innovation for everyone and it makes me mad.

If these companies don't get broken up with a competitive mobile OS landscape again, don't get mad when I jump ship and go with some OS Huawei makes if it offers the right way and gains adoption.

If America wants competitiveness, innovation and a technological lead, it has work to do at home: Trust busting needs to happen fast.

Add to that a bit of science nationalism from the De Gaulle era, and we ended up with that app.