[Ssc-dev] eyeWitness/InformaCam update

[John Shrives]

Bryan

Thank you again for a very useful, and hopefully one of many , comprehensive update.

Regarding the questions below we would like the following:


1)      Default option in setup is to save image as part of app but allow to change in preferences as per your NOTE

a.       We imagine that if people wish to send  captured images to other than the IBA they can change the option to access the as taken images in their gallery and send them from there

2)      Default option in setup to "auto-logout" but allow change in preference as per your NOTE

a.       We would need to warn people of the vulnerability of leaving the app open

b.      How long a time would you set before the auto-logout kicks in or would this be a preference parameter as well?

3)      Please keep the language options with the default as English

4)      We would like the option to input an e-mail address but this should not be mandatory field

5)      I understand Tim has already re-sent you the icons / graphics

Any questions then please let me know otherwise I look forward to catching up with you again at next week's Scrum.

Have a good weekend

All the best

jms

From: bryan [mailto:bryan.nunez at gmail.com]
Sent: 04 July 2013 01:14
To: Mark Ellis; Tim Licence; John Shrives
Cc: Harlo Holmes (harlo.holmes at gmail.com); David Oliver; Mikael von Pfaler; ssc-dev at lists.mayfirst.org; Carrie Stiens Winfrey
Subject: Re: eyeWitness/InformaCam update

Dear Mark,Tim and John,

As a follow up to point #2 from yesterday's email, Carrie and Dave worked on streamlining the user experience and Carrie put together  some new mockups of the workflow.  Dave has provided the narrative below.  Please take a look and let us know what you think.

There are also 5 questions at the bottom of Dave's report to help clarify some points on the workflow.  If we can get answers to those questions ASAP we can begin implementing right away.

Please let us know if you have any questions.

Thanks!
Bryan


PROGRESS REPORT

We've now arrived at a new application (device-side) workflow, simplified both visually and as a process.  Due to the time-pressure we're providing only screenshots, not a comprehensive prototype, so I will provide a bit of narrative:

client side workflow redesign: eyewit_ui_improv.png<https://dev.guardianproject.info/attachments/download/761/eyewit_ui_improv.png>

A user would reach this set of screens by tapping on an image in the image gallery (no design work on the gallery yet).  Our new design has a VIEW mode and an EDIT mode.  In VIEW mode, the user will either commencing EDITing, or choose to send the image.  VIEWing supports: (a) seeing certain of the static metadata, (b) seeing already-added free-text, (c) seeing already-added forms and (d) listening to already-added audio notes.  EDIT mode supports: (a) addition of audio notes, (b) addition of free-text notes, (c) addition of tags.  Note that only tags have the option to carry form-type text.  Form entry will not be as shown in this mock-up - we'll instead of a single form-entry screen.

In this design, audio notes are for the "internal" use only.  That is, they are "crib notes" for use in adding forms or free-text.  They will not transit the network or be stored with the InformaCam-inflated image.  We can revisit in a future release if necessary.

The process of sending an image to IBA will happen in the background.  When the user selects "share with IBA", that action will pop up a 5 second message indicating same, and then later a message will appear in the Android notification bar.

Our programmer has reviewed, and this design is achievable in the timeframe we've got.

setup screen redesign: eyewit_setup<https://dev.guardianproject.info/attachments/download/767/eyewit_setup_%20.png>

We are working to minimize the setup screens, though there are still questions remaining (see below).  Since we're "wiring" this app to IBA as the "home base" we can likely remove many previously-available options.  Or simply hard-code them in this release.

The primary change is to make the key generation process happen in the background.  We will have additional clarity in the next few days, with some new screens, but the important point is that the user will not perceive that they are waiting for that process to complete.

REMAINING: We are doing a review of the Gallery part of the app now, and may have more simplifications there too.

Questions:

1. We currently offer the option keep images in an as-taken, un-encrypted, un-inflated form on the device, viewable in the Android gallery.  SInce we are wiring this version to IBA's individual needs, I'd prefer a policy statement here (either we keep them or we don't) rather than expose a choice.  What would that choice be?

2. Similarly, we currently have an "auto-logout" preference.  Can we instead have a policy statement here as to auto-logout?

NOTE: in #1 and #2, we could propose eliminating the act of setting the preference, but keeping the setting in the preferences panel to allow changing it later (just not during "setup")

3. Do we need language options? These are in the current build.

4. Do we need to get an email address? This is also in the current build, but not in the new design.

5. Branding? We've made un-branded screens in the mock-ups.  We need a launcher icon, a loading/startup graphic and a color scheme that matches.  Need a timeline for these items.

As I said, we feel good about accomplishing the new design in the shot time-scale we've got.  We think the simplifications really work nicely, and we hope to get more by streamlining setup options (the questions we asked).  Our new developer is already working on this.

Regards,


Dave O

On Tue, Jul 2, 2013 at 12:32 PM, bryan <bryan.nunez at gmail.com<mailto:bryan.nunez at gmail.com>> wrote:
Hi everyone,

Dave, Barbra, Mikael and I met briefly during our scrum session but since some of the team weren't able to join, Dave and I thought it would be good to send out a general update.


0. Nathan provided a powerpoint<https://docs.google.com/presentation/d/19Rx6nJHUf6Au4aU-V_iP4u3PK2Tj04jtKGlaK3HDf5U/edit?usp=sharing> describing overall status late last week.

1. We have a new build of the mobile application, with significant work on functional stabilization.  Just released, this obviously needs to be tested.  Nathan's prior memo addresses some points to that effect.  Both Tim and I have experienced crashes during the setup.  See the ticket here<https://dev.guardianproject.info/issues/1553>.

2. We spent significant time re-thinking the user experience of the core workflow (in the mobile app), and our designer Carrie has done a redesign, available as screenshots (not yet a functional mock-up).  Our new developer Mikael is already looking at that to assess the work.

3. We also spent significant time re-thinking the "setup" process for the mobile app.  Our designer is currently working on that redesign, and we hope to have screenshots for that by Thursday.  Our developer will assess that, also this week.

4. We have a new developer active on the "j3mifier" tool which sits between the mobile app and the analytics functions sitting on the server side.

5. Dave is working with the server/analytics developer on re-planning for an incremental deliver of server/analytics function.  We will have that within 48 hours.

If you have any questions please let me know and continue to file bugs on the tracker.

Best regards,
Bryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/ssc-dev/attachments/20130705/88a8c3fc/attachment-0001.html>