Confused about Users API
David Walt
I would like to create a website, using "Users API", because as you
all know, it provides lots of help to handle log in/out, security,
etc. Reinvent the wheel would be stupid I guess.
But, and this is huge BUT, you are forced to use Google account (or
OpendID).
The problem is:
if future users of my website must create a google account before
using my website, they must go to another website (the google's one in
this case). And even its not a problem for you, trust me, your grandma
would leave the website as soon as the page would change. And my
future clients will be grandmas...not developers.
I'm very afraid of losing lots of clients by forcing them to create a
google account in order to connect my website.
More, I would like to create a really really fast subscription (just 2
fieds to fill and it's done).
So, what to do ?
- Create my own user management system, losing lots of time, and
knowing that the code will be shitty?
- Use the google Users API and take a big risk that my future client
does not feel like to subscribe?
- Maybe use a Java Framework which provides the same functionnalities
that Google API, but with any kind of client?
I really need your ideas for this!
Thanks a lot guys.
Branko Vukelic
> - Maybe use a Java Framework which provides the same functionnalities
> that Google API, but with any kind of client?
This is probably the best solution if you don't want to use a 3rd
party service like Janrain. Of course, depends on the framework. It
could be the worst solution for everything else and even auth if you
use a bad framework. :)
--
Branko Vukelić
bra...@herdhound.com
Lead Developer
Herd Hound (tm) - Travel that doesn't bite
www.herdhound.com
David Walt
If I use a framework, can I use it just for this, and what about the
performance ?
(sorry it's begginers questions)
On 1 juil, 15:27, Branko Vukelic <bg.bra...@gmail.com> wrote:
> > - Maybe use a Java Framework which provides the same functionnalities
Branko Vukelic
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>
--
Branko Vukelić
bra...@herdhound.com
Lead Developer
Herd Hound (tm) - Travel that doesn't bite
www.herdhound.com
Love coffee? You might love Loveffee, too.
loveffee.appspot.com
Stephen
> Hi guys,
>
> I would like to create a website, using "Users API", because as you
> all know, it provides lots of help to handle log in/out, security,
> etc. Reinvent the wheel would be stupid I guess.
>
> But, and this is huge BUT, you are forced to use Google account (or
> OpendID).
Use openid, but be your own openid provider. Now you get to control
the sign-up experience but reuse Google's auth cookie and user api.
David D.
Thanks Stephen, it seems to be a good idea.
But unfortunately, even if openID is a great idea at the beginning,
time has shown than users are completely lost with openID, and it
would explain why this concept didn't have the success that it really
deserves.
Whatever, I'll take a deeper look to this solution. Because finally,
if users can suscribe without beeing confused, that's the only thing
which matters for me.
I guess I could even not telling them than they are creating an openID
when they're suscribing?
Thank you very much.
On 4 juil, 06:08, Stephen <sdeasey+gro...@gmail.com> wrote:
> > I would like to create a website, using "UsersAPI", because as you
Stephen
>
> I guess I could even not telling them than they are creating an openID
> when they're suscribing?
That's the idea. They don't need to know. You're just using it as a
mechanism to get Google to drop a cookie on your domain. You control
the whole user experience.
