==Overview==
Mozilla Presence provides a measure There are two levels of a users liveliness to applications the user has chosen to share it with as well as a system that allows for lively notifications to be delivered to the user regardless of if the local application is running.presence:
The 1/ app-level presence * online: you are connected in the app, and using it * offline: you are disconnected from the app 2/ device-level presence. * online : you are using your FXOS phone or your desktop browser* offline: you are not on your FXOS phone or your browser Sometimes you might be online in 1/ or 2/ and not wishing other users to know about it. And you also might want to appear online for app B but not for app C. 1/ is solved by every application. they all have their ad-hoc system, their social graph, rosters, contacts, etc. Large social networks don't care as much about 2/ because they would prefer you to use *only* their application must register with for talking to your friends. By solving 2/, we can enable non-dominant social/communication applications to get useful presence information they can act on. Mozilla Presence an Internetacts as a trusted intermediary between the user's device (solving 2/) and the applications the user has allowed to see their presence, as well as a short-reachable end-point lived notification system for user presence updates to be sent applications toengage available users.
==Project Contacts==
Note: Lively notifications are different than SimplePush style Notifications in that they can require immediate action else they'll become stale, like a missed phone call.
The project will be a success if an application registered with Mozilla Cloud Services is able to reach out to users that are "online" (active on their phone or desktop but with the app not running)via Mozilla Presence.
==Use Cases==
