Difference between revisions of "OpenID in Smartphones"
From MgmtWiki
(→Full Title or Meme) |
(→Full Title or Meme) |
||
| Line 2: | Line 2: | ||
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]]. | 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 | + | ==Context== |
* This use case assumes the user with a [[Smartphone]] that want to enable a [[Self-issued Identifier]] using only that phone | * This use case assumes the user with a [[Smartphone]] that want 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. | ||
==References== | ==References== | ||
[[Category: Identifier]] | [[Category: Identifier]] | ||
Revision as of 21:07, 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 want 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.
