First, make sure you look at this:
Second, that seems like a very elaborate workaround for the problem that only helps people
with Wear devices. I'd rather find a way to do direct insertion.
Now, I'm not opposed to Wear support in general. I just want to see a clear design so
that we can get the UX issues right.
----- Original Message -----
Some apps have awful OAuth sign-in interfaces where leaving the app
get an OTP causes the login cycle to restart, so I need to re-enter my
(long) email and (longer) password before I can log in. When my phone
lags or I start to mistype my credentials, this starts to become a
This isn't a problem with the design of FreeOTP, of course; it's a
problem with the applications that don't have persistent sign-in
setups. But if FreeOTP had an Android Wear interface, people with
watches connected to their phones could just open up the watch
application when they need a code and never have to start a new intent
on their phone.
This would involve an optional Google Play Services dependency (which
is already required by Android Wear). My biggest concern would be
sending data over to the watch without exposing the private key to
Google's cloud, because many of the messaging APIs allow watch data to
sync using Google's servers. Perhaps a better solution would be to
send individual OTPs as they are requested by the watch app. I'm not
sure how, exactly, this should be implemented, but I would love to see
it included in the app.
I'd be willing to start development if no one else is interested.
freeotp-devel mailing list