<div dir="ltr">Hey Liron,<div><br></div><div>We definitely are interested in modernizing the ChatSecure iOS UI/UX with a focus on usability for new users, while encouraging/enforcing good security practices. The reason the iOS and Android UI is so different right now is that we were two separate projects with similar features that just recently merged branding. The approach we take on iOS is minimalistic, with a desire to keep the chat interface familiar and somewhat similar to the standard iOS text messaging app.</div>
<div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 6, 2014 at 1:02 PM, Liron Tocker <span dir="ltr"><<a href="mailto:lirontocker@gmail.com" target="_blank">lirontocker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for the warm welcome and for introducing me to some of the issues you guys are currently working on.<br>
<br>
I’ve only been using ChatSecure for about a week so I’ve got some catching up to do, but perhaps my perspective as a new user might be valuable as well.<br>
<br>
A few thoughts off the top of my head:<br>
<br>
Telegram are essentially following the same basic design patterns that most modern instant messaging systems use. The decision if ChatSecure should do the same boils down to the goal of the project and what it’s ultimately trying to accomplish. As far as I see it, If we want to introduce new users to encrypted messaging it’d be a good idea to create an interface with a minimal learning curve - which means: A) adhering to the UX a user would expect from an instant messenger and B) introducing unfamiliar interactions (such as verifying an OTR session) in a way which users can easily learn and keep in mind (sorry for this being totally vague, I can’t be more concrete before hacking at wireframes for a while).<br>
<br>
I’d say that both iOS and Android should have a very similar user experience (each adhering to the interface guidelines of their respective platform), unless it’s not technically feasible. It is the same product on both platforms, but of course there’s always the possibility of taking advantage of the unique hardware/software of a specific platform in order to do something cool. At first, though, I’d concentrate on getting a consistent and user-friendly interface running on both.<br>
<br>
I think what I’d like to do would be to talk one-on-one with the iOS and Android devs to get a better understanding of what thoughts and ideas they have regarding the interface - I’d also like to hear your thoughts regarding the reasoning of some of the design decisions you’ve made. I’d then go ahead and start working on some paper sketches so I can form some more concrete ideas regarding specific improvement of user flows and layouts. I’d make sure to send you guys frequent updates - I’m a fan of releasing early and often :)<br>
<br>
If you guys are okay with group voice chats, that’d be a great way for me to get feedback as well.<br>
<br>
Greetings from Hamburg,<br>
<br>
Liron<br>
<div><div class="h5"><br>
<br>
<br>
On 06 Jan 2014, at 20:39, Nathan of Guardian <<a href="mailto:nathan@guardianproject.info">nathan@guardianproject.info</a>> wrote:<br>
<br>
> On 01/06/2014 02:13 PM, Liron Tocker wrote:<br>
>> I’ll cut the rambling - thanks for reading this far. Please let me know<br>
>> if you guys think that this kind of work would be useful for you, and if<br>
>> it is - we can figure out how to get the ball rolling.<br>
><br>
> Yes, absolutely, and it seems you would be a great fit to get that ball<br>
> going! We currently have three developers working on ChatSecure Android<br>
> and two working on iOS. Most of us are on this list.<br>
><br>
> Here are a few question / areas to begin with:<br>
><br>
> 1) Should we follow Telegram.org path and essentially just clone the<br>
> WhatsApp / Line / WeChat user experience? How closely should the Android<br>
> and iOS experience match? Again do existing popular messaging apps<br>
> provide a guide here?<br>
><br>
> 2) We have been working recently on indicating encryption/security state<br>
> using more subtle color bar indicators, but how can we make the<br>
> security/privacy aspects of using the app more existing and compelling<br>
> (both visually and experientially)? Verification of OTR session is<br>
> critical, but most people don't do it still... how do we change that?<br>
><br>
> 3) While I personally love our swipe-based interface for moving between<br>
> open chats, I know some do not. I feel it provides a rapid mechanism for<br>
> moving between multiple active conversations, and provides a bit of<br>
> unique flair, beyond the typical contact list / conversation type flow.<br>
><br>
> 4) How do we simplify the setup process so that people can get connected<br>
> to their existing identities/accounts (google, facebook, <a href="http://jabber.ccc.de" target="_blank">jabber.ccc.de</a>)<br>
> or create an entirely new one in a streamlined friendly manner?<br>
><br>
> Thanks and excited to have your help.<br>
><br>
> +n<br>
><br>
> _______________________________________________<br>
> Guardian-dev mailing list<br>
><br>
> Post: <a href="mailto:Guardian-dev@lists.mayfirst.org">Guardian-dev@lists.mayfirst.org</a><br>
> List info: <a href="https://lists.mayfirst.org/mailman/listinfo/guardian-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/guardian-dev</a><br>
><br>
> To Unsubscribe<br>
> Send email to: <a href="mailto:Guardian-dev-unsubscribe@lists.mayfirst.org">Guardian-dev-unsubscribe@lists.mayfirst.org</a><br>
</div></div>> Or visit: <a href="https://lists.mayfirst.org/mailman/options/guardian-dev/lirontocker%40gmail.com" target="_blank">https://lists.mayfirst.org/mailman/options/guardian-dev/lirontocker%40gmail.com</a><br>
><br>
> You are subscribed as: <a href="mailto:lirontocker@gmail.com">lirontocker@gmail.com</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Guardian-dev mailing list<br>
<br>
Post: <a href="mailto:Guardian-dev@lists.mayfirst.org">Guardian-dev@lists.mayfirst.org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/guardian-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/guardian-dev</a><br>
<br>
To Unsubscribe<br>
Send email to: <a href="mailto:Guardian-dev-unsubscribe@lists.mayfirst.org">Guardian-dev-unsubscribe@lists.mayfirst.org</a><br>
Or visit: <a href="https://lists.mayfirst.org/mailman/options/guardian-dev/chrisballinger%40gmail.com" target="_blank">https://lists.mayfirst.org/mailman/options/guardian-dev/chrisballinger%40gmail.com</a><br>
<br>
You are subscribed as: <a href="mailto:chrisballinger@gmail.com">chrisballinger@gmail.com</a><br>
</div></div></blockquote></div><br></div>