@larand True but at least prompting the user could help insure they at least decide what if any security works best. Assuming finger print or not at all is rather weak. But at least those who pay attention can remedy that after the setup is done.
Twice now I've gone through the process of setting up an Android device in the last week. Both times when it gets to the finger print setup I've hit the skip button and it continues on without any further security setup. Wouldn't it make sense to ask about a password or pin after that rather than assume the user doesn't want security?
So I started looking through the various bits of code I had tossed together for 10C (including BlurbyBot) and boy is it messy. I'm very tempted to start a clean implementation and make it fully open source. Possibly even splitting out the API calls into a library module for others to re-use.
I should actually ask though has anyone put together a library for the 10C API yet?
@jussipekonen Are you planning on a particular framework or just doing native? I'm thinking about adding some 10C into my mix again and wondering if it's something I could potentially contribute to.
// @larand
@jussipekonen when you do get around to being able to work on it would it be an open source project?
// @larand
It's been a while since I've kept up with the goings on in this neck of the internet woods. I don't recall but is Cappuccino still pretty much it for Android these days or has someone hacked together a client yet?