<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">HI Jordan,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 25, 2019, at 4:05 PM, ♠ Jordan Reiser ♠ <<a href="mailto:jordan.l.reiser@gmail.com" class="">jordan.l.reiser@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div dir="auto" class="">I think the information is designed clearly but q bit dense and is in need of some modernization. I’m just becoming familiar with it and haven’t had a chance to review the app in its current form on desktop or mobile yet (just seen screenshots so far). I have some initial ideas though ,</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""> 1. for example does the user need to see everything all at once or can things be shown only when the user needs it, thinking of collapsing information inside of different interactive access controls, eg onclick panels, accordions, sliders etc., basically leveraging invisible space as much as possible so the user can focus on a few things at a time. </div></div></div></blockquote><div><br class=""></div><div>We use a more pedestrian way of doing just that - you can see it in the screen shot, actually. We have multiple tabs. The first one shows the most useful information for a user looking at a dive (screenshots from a Mac as that what I'm on right now)</div><div><br class=""></div><div><img apple-inline="yes" id="6D753A7D-B7F0-4434-8F71-263F017A5933" width="493" height="409" src="cid:B1FD5B25-CC90-4AF8-8CB9-F07F11073986" class=""></div><div><br class=""></div><div>Then we have information about some of the equipment used (that one I find particularly ugly).</div><div><br class=""></div><div><img apple-inline="yes" id="4B9A67A4-5931-4EE0-B2D3-E63B0B70AEBA" width="500" height="412" src="cid:605BF3D5-F8A9-4256-9B98-85FF8C0ADCA8" class=""></div><div><br class=""></div><div> A lot more information about THIS dive. </div><div><br class=""></div><div><img apple-inline="yes" id="AA7333CB-8AE6-4F42-9833-975479BF26BC" width="492" height="410" src="cid:51705536-7848-47A1-9827-142A66D29131" class=""></div><div><br class=""></div><div>And then the statistics tab that shows information about all selected dives (this is kinda boring with just one dive selected).</div><div><br class=""></div><div><img apple-inline="yes" id="9FA4C783-F3F7-45E5-89E9-66557382DD0C" width="497" height="401" src="cid:8E668795-6CC9-424D-9B79-B1EFE6232EF5" class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div dir="auto" class="">2. Given the above maybe there is a way to combine the information contained in the tabs to lessen the amount of tabs needed, just rethinking the nav and consolidating similar areas may help it feel like less even though its the same amount of info.</div></div></div></blockquote><div><br class=""></div><div>I'm very open to better ideas here. The current layout is driven by the need to work on relatively small screens (it's not unusual for divers to bring an old laptop with a 1280x800 screen - I don't think we support 1024x600 anymore... we used to).</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div dir="auto" class="">3. Visualizing stats wherever possible, eg. gas consumption can be visualized against the total perhaps, things like this.</div></div></div></blockquote><div><br class=""></div>Again, very open to better ideas. Our two main constraints so far have been "finding great design" and then "with the design ideas we have, finding how to implement them given the UI toolkits we have decided to use". Moving to different UI toolkits is a very, very, VERY tall hurdle. I can talk for hours about why (Bryan heard a really short version of that last week).</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div dir="auto" class="">Give me a day or so to take a hard look and can spin you guys up something cool</div></div></div></blockquote><div><br class=""></div>Of course! We'd love to see it.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div dir="auto" class="">Noob question i have right now is, can users log data only manually is it possible to do semi or fully automatically? This app reminds me of a snowboarding app i once had, does similar things going to look for some inspo there. </div></div></div></blockquote><div><br class=""></div><div>You can manually enter dives. You can download from a simple dive computer and add more data manually. And you can download data from a sophisticated dive computer and get a lot of the information filled (e.g., a simple dive computer gives you no information about the gas use, a better one might include that).</div><div><br class=""></div><div>/D</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><br class=""></div><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 25, 2019 at 5:53 PM Dirk Hohndel <<a href="mailto:dirk@hohndel.org" class="">dirk@hohndel.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 24, 2019, at 10:09 AM, Willem Ferguson <<a href="mailto:willemferguson@zoology.up.ac.za" target="_blank" class="">willemferguson@zoology.up.ac.za</a>> wrote:</div><br class=""><div class=""><div class="">Attached a screenshot of a concept of rearranging the statistics tab. The old design was not space efficient. This one provides all the information in the statistics tab of the present master. Important thing is that it frees a fairly large area at the bottom of the tab. The plan is to use this for more detailed graphical analyses such as bar charts of continuous variables and pie charts of categorical variables. The text box on the right with gas consumption information gets a scroll bar when the tab is made more narrow. Sometimes, with deco dives having 5 or 6 gases, the text in the text box can exceed the depth of the box. In this case a scroll bar appears and allows viewing all the text.<br class=""><br class="">Would this be workable at all?<br class=""><br class=""><img name="m_8208646698176892041_StatisticsTab1.png" style="max-width: 100%;" class="" apple-inline="yes" id="65445DFC-E9E5-4172-9CE8-7255E6F71B02" src="cid:16ea4fa4ec917690ef81"></div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">I'm always sad when one of us comes up with an idea for the UI and there are no comments at all.</div><div class="">There are several hundred people on this mailing list, most of whom I think use the software. So it feels odd that no one would care.</div><div class=""><br class=""></div><div class="">To me it looks less sophisticated. It looks very 1990-s :-)</div><div class="">Yes, definitely much more space efficient. But I really hope that we can come up with something that is more attractive than this...</div><div class=""><br class=""></div><div class="">Jordan, this is where someone with a design background might be extremely welcome... but I don't want to put you on the spot :-) :-) :-)</div></div><div style="word-wrap:break-word" class=""><div class=""><br class=""></div><div class="">/D</div><div class=""><br class=""></div></div></blockquote></div></div>-- <br class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Jordan Reiser<br class="">Experience Designer @ SparksGrove, a Division of North Highland<br class=""><br class="">973.930.3206<br class=""><br class="">--<br class=""><a href="http://Linkedin.com/in/jordanreiser" class="">Linkedin.com/in/jordanreiser</a><br class="">Rentbuybash.com<br class="">Splantern.com<br class=""><br class=""><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>