[quonn]

It doesn‘t work great. I actually run it on my phone. It has silly bugs, despite the simplicity.

Additionally, for that price you could have easily have 3 independent teams develop it and take the best one and still be cheaper and better.

I hope someone will challenge this in court. I don‘t think they can get away without a call for bids which should have been done (across Europe, as the law requires).

[johannes1234321]

Yes it has bugs, but most bugs are from the system framework ... they could have handled those better, but the cause is often out of their control

[rkachowski]

In what sense are most of the bugs from the "system framework"?

[johannes1234321]

There is this contact tracing framework in iOS and Google Play Services and that causes a few errors. Some users get a message like "not possible in your region" and some get some random error codes about rate limits and such errors, which bubble up from those frameworks and can only be fixed there.

[quonn]

Yeah. It‘s the framework which does pretty much all of the interesting technical work, if I may say so. It does the communication with other phones and determines if there was a contact and generates, stores and maintains the tokens and given the server data figures out matches and so on. It has a tiny, simple to use API on top.

It was jointly developed by Apple and Google. For free.

[rkachowski]

That's what I thought, it seems that the entire project is basically a fancy wrapper around the Exposure Notification apis provided by Apple and Google.

There's some kind of cognitive dissonance around your idea that these companies deserve so much compensation for designing a solution that relies so heavily (entirely) on these features, and yet be free from responsibility for serious bugs that arise from this decision.