search

mozilla / persona-roadmap

A repository for user stories related to Mozilla's Identity efforts.
3 stars 1 forks source link

As an RP developer, I want a simpler navigator.id API so that it is easy to integrate Persona with my site. #15

Open shane-tomlinson opened 11 years ago

callahad commented 11 years ago

When we polled the mailing list, the desire to reform .watch() was only raised by MoCo employees on the Persona team. I suspect we're being overly sensitive -- most RPs are just using libraries, which only have to be rolled once.

shane-tomlinson commented 11 years ago

@callahad - I suspected this too, until I got down and dirty with the API. After spending man days figuring edge cases out, I have empathy for end developers who are trying to jury rig Persona into their current architecture. It's not fun.

seanmonstar commented 11 years ago

I actually had no interest for myself, but I've spoken with a couple folks in webdev that found it painful. Especially the maintainers for django_browserid, like mkelly.

r0bl0rd commented 11 years ago

Sounds like this is still open then? Benefit? Priority? What stage of RP adoption blocked?

callahad commented 11 years ago

I can see it blocking understanding or deployment. We're having a lot of people get all the way into deployment, then realize they didn't understand wtf .watch() does. It's a Bad Surprise.

fmarier commented 11 years ago

Also, it's making it hard/impossible to add Persona to some frameworks or to write plugins. Two concrete examples: the hacks that were needed in django-browserid and wordpress-persona.