Ripple for mobile is an attempt to understand communication through mobile devices. Our main goal is to understand user behavior and find bottlenecks in our existing technological framework in an effort to streamline technical issues to reduce friction in communication.

Like in many aspects of life, it is crucial to think about authentication and authorization. When I get a message, how can one be assured that it is from the entity it claims to be from? When you are sending a message, how can you be assured that only the intended recipient will have access to the message?

If users are burdened with having to check the identity of the other party manually, it reduces the flow of information. It should be possible to offload authentication and authorization to a third party without the user having to force themselves through this process.

Last edited May 1, 2013 at 4:54 PM by ripplemobile, version 1


No comments yet.