<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true"><br></div><div><div>On Jun 6, 2013, at 1:51 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 6, 2013 at 2:38 AM, Deepali Khushraj <span dir="ltr"><<a href="mailto:dkhushra@redhat.com" target="_blank">dkhushra@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap:break-word"><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
Sorry I am chiming in late.</div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
I like the mock-ups. A few comments:</div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
* It seems from the designs that the user can add only a single OS-specific variant per app. For example, I can create "Mobile HR" app with a single "HR iOS" variant, but not two variants like "HR iPad" and "HR iPhone free". I believe Matthias' lexicon states such multiple variants are possible per app. . </div>
</div></blockquote><div><br></div><div><br></div><div style="">yes. HR-iPad, HR-iWatch, HR-Android-watch, HR-Android-Tablet etc</div></div></div></div></blockquote><div><br></div><div>Hylke: I didn't hear back to you on this, so asking again.</div><div><br></div><div>How would the user provide names for these mobile app variants using current designs? I don't see a field to capture this. </div><div><br></div>Also I think a separate area maybe required to show the user API credentials (app keys/secrets etc.)-- required to start using the PushEE REST API. </div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
I think the way you've done is fine. However, if we choose this path then, I think, we need to update the specification and ensure the REST API won't allow multiple OS-specific variants per app, otherwise, they can't be shown in the UI. </div>
</div></blockquote><div><br></div><div><br></div><div style="">see above</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
* Apple's Push network has prod and dev environment options, a flag would be useful.</div></div></blockquote><div><br></div><div>See <a href="https://issues.jboss.org/browse/AGPUSH-88">https://issues.jboss.org/browse/AGPUSH-88</a><br>
</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="margin:0px;font-size:12px">* The terms "Instance" and "Variant" will be unfamiliar terminologies to a new user. A help icon on the screen or just some text explaining the meanings of these terms to new comers would be helpful</div>
<div><br></div><div>* <span style="font-size:12px">Terminology suggestion:</span></div><div style="margin:0px;font-size:12px"><span style="white-space:pre-wrap"> </span>Instance -> "Active user instances" or just "User instances"</div>
</div></div></div></blockquote><div><br></div><div style="">"active" implies running ? User instance is better...... basically it's the installation of the actual app</div><div><br></div><div><br></div><div><br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div><br></div></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
* I found the name <span style="font-size:12px">"Variants and Push Networks" confusing. I would suggest we use one :) </span></div></div></blockquote><div><br></div><div style="">Not sure I follow (variant != Push Network)</div>
<div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
* I<span style="font-size:12px"> noticed you added links to download client SDKs, which is great. </span><span style="font-size:12px">I think a link to the Sender REST API spec would be useful too.</span></div><div><br></div>
<div>* I found our iOS tutorial to be really helpful. It got the user up and running really quickly. This is something I struggled with Urban Airship and other services. Linking ours to the console could be a real value add to first-time users </div>
</div></div></blockquote><div><br></div><div style="">"Help" section? Has links to SDK, tutorial etc ??</div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><br></div><div>* <span style="font-size:12px">We need to check the security aspect of showing end-user emails in the instances tab to the developers of the app. </span></div></div>
</div></blockquote><div><br></div><div style="">Well, it can be some other aspect. But .... the developer of company X will be able to query all users for company X...</div><div style="">It's not that Manager of company Y sees them.<br>
</div><div style=""><br></div><div style=""><br></div><div style="">If you feel this is really important, please open a JIRA</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><span style="font-size:12px"><br></span></div><div>* Also, if an app gets really popular then this list will likely be really long, like thousands of users. Not sure if our console could handle that. I think this feature of being able to see instances is great in "development mode" or during apps' "beta testing" though.</div>
</div></blockquote><div><br></div><div style="">Pagination will be there, At least I was expecting that, even if the mockups do not show that.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div>* <span style="font-size:12px">Is the check-mark in first screen used to make an app active Vs inactive?</span></div></div></blockquote><div><br></div><div style="">
He will do that in a later round, Hylke said</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><br></div><div>* I like that you show the variants summary in first screen, wondering if we could use icons there for iOS, Android & web.</div><div><br></div><div>* I was wondering if we could consider some UX ideas for first-time user experience. I imagine a lot of users using this service would never have used Push before, so they may need some hand holding and the UI is a great way to start that.</div>
<div><br></div><div>I am compiling a list of future use cases, will share that on the list next.</div><div><br></div><div>What you have is already very nice.</div><div><br></div><div>Thanks!</div><span class=""><font color="#888888"><div>
Deepali. </div><div><br></div><div><span style="font-size:12px"><br></span></div><div><span style="font-size:12px"><br></span></div><div><br></div><div> </div><div><br></div><div><br></div><br><br>
</font></span></div><div><div class="h5">
<br><div><div>On Jun 4, 2013, at 11:26 AM, Hylke Bons <<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>> wrote:</div><br><blockquote type="cite">Hi,<br><br>It seems that most of us are happy with the wireframes for the Unified <br>
Push Server admin UI. I've used the feedback to make a few small <br>changes: <br><a href="https://github.com/hbons/aerogear-design/blob/master/aerogear_unified_push_server_admin_ui.png" target="_blank">https://github.com/hbons/aerogear-design/blob/master/aerogear_unified_push_server_admin_ui.png</a><br>
<br>The next step is to look at the the missing features like the user <br>management and authentication. It would be good to have a discussion <br>about this, and I have some questions too.<br><br>If I understand things correctly, the Push Server can run "standalone" <br>
or as a component in JBoss AS (or something else). So we'll need a UI <br>for user management when we run standalone, but one that can be disabled <br>and be plugged in by different existing auth systems that are running on <br>
the server or somewhere else.<br><br>Some questions that come to mind:<br><br>How is the server bootstrapped? And how is the initial user account <br>configured? The most essential basic role would be to access the UI and <br>
to configure push notifications (and one to add other (admin) users). <br>Are there any other roles that we should be considering? Things that <br>should be disabled for some users?<br><br>Thanks,<br><br>Hylke<br>_______________________________________________<br>
aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br></body></html>