Setup Wizard

[GoogleCodeExporter]

We need a replacement for the stock setup wizard. All it really needs to do
is take the login info from the user. We need to document the database
structure used so that other apps can access the login data for single-signon. 

As the sync manager is going to support more than just Google, we should
consider another database/table with the list of available sync handlers so
the user can choose which one they want to use from the setup wizard. 

Do we need to have more than type, user, and password? 

Original issue reported on code.google.com by ttab...@gmail.com on 26 Sep 2009 at 3:25

[GoogleCodeExporter]

Original comment by ttab...@gmail.com on 26 Sep 2009 at 3:48

[GoogleCodeExporter]

Please implement multi-service login credential storage. For starters, start 
with
Google login credentials, but allow UI extensibility for adding Twitter, 
Facebook,
Yahoo, MSN, etc. as separate account credentials. Provide intent feature for 
calling
credentials data so future apps (such as a multi-IM applications) could draw 
accounts
from the Setup Wizard, rather than require per-app inclusion of data. Sort of
social/sync Keychain for Android.

Original comment by rayner...@gmail.com on 29 Sep 2009 at 3:11

[GoogleCodeExporter]

One thing that would be neat is an OpenID store.  e.g. configure the device to 
use your 
OpenID identity with built-in OAuth support.  I don't know enough about OpenID 
to 
know whether this makes sense on a phone, but if it's possible it would be 
really cool.

Original comment by morri...@gmail.com on 29 Sep 2009 at 5:50

[GoogleCodeExporter]

Morrildl, I am not sure about the usability of OpenID support but if the 
credentials
storage supports multiple logins for multiple services each with its own data 
layout
(login/pass by default, but URL for OpenID), it falls in the "hell why not?"
category. A multi-service credential storage would reply to intents from apps 
asking
for login data for specific services, so if AOA credential storage becomes 
popular,
third-party apps would only have to sent an intent and spare the user having to 
enter
login information for every other app he installs, i.e. OpenID for any app that 
needs
one. Although, OpenID is hardly the used login service for mobile apps. 

Original comment by rayner...@gmail.com on 29 Sep 2009 at 5:59

[GoogleCodeExporter]

JBQ has already written an app that will properly provision AOSP builds that are
missing the setup wizard.  This particular fix has nothing to do with user gmail
credentials.

https://review.source.android.com/#change,11991

PERTINENT CODE:
// Add a persistent setting to allow other apps to know the device has been 
provisioned.
35          Settings.Secure.putInt(getContentResolver(),
Settings.Secure.DEVICE_PROVISIONED, 1);

Original comment by trevor.e...@gmail.com on 29 Sep 2009 at 7:48

[GoogleCodeExporter]

Hi there, this sounds familiar. We're working on an OAuth client for Android. We
should have something working this weekend: 
http://github.com/novoda/oauth_for_android

Original comment by novo...@gmail.com on 30 Sep 2009 at 10:53