Difference between revisions of "OpenID in Smartphones"
From MgmtWiki
(→Context) |
|||
| Line 6: | Line 6: | ||
* Both Apple and Android have learned that energy consuming applications will drain a user's battery and work to limit apps that do that. | * Both Apple and Android have learned that energy consuming applications will drain a user's battery and work to limit apps that do that. | ||
* Also no app that resulting in huge drains on the [[Smartphone]] battery would survive for long in the marketplace. | * Also no app that resulting in huge drains on the [[Smartphone]] battery would survive for long in the marketplace. | ||
| − | * The | + | * The goal for would be a [[Self-issued OpenID Provider]] [[User Experience]] that is as good as the front channel [[OpenID Connect]] experience. |
==References== | ==References== | ||
[[Category: Identifier]] | [[Category: Identifier]] | ||
Revision as of 21:12, 7 December 2020
Full Title or Meme
This use case focuses on the parts of enabling a Self-issued Identifier within a battery-powered mobile device that will impact the protocol that is used when the device acts as a Self-issued OpenID Provider.
Context
- This use case assumes the user with a Smartphone that wants to enable a Self-issued Identifier using only that phone
- Both Apple and Android have learned that energy consuming applications will drain a user's battery and work to limit apps that do that.
- Also no app that resulting in huge drains on the Smartphone battery would survive for long in the marketplace.
- The goal for would be a Self-issued OpenID Provider User Experience that is as good as the front channel OpenID Connect experience.
