<br><br>On Wednesday, June 26, 2013, Lucas Holmquist wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>On Jun 17, 2013, at 8:19 AM, Hylke Bons <<a href="javascript:_e({}, 'cvml', 'hbons@redhat.com');" target="_blank">hbons@redhat.com</a>> wrote:</div>
<br><blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello,<br>
<br>
I've updated the wireframes with the points raised, you can find
it here:
<a href="https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push_server_admin_ui.png" target="_blank">https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push_server_admin_ui.png</a><br>
<br>
I'll address your feedback inline.<br>
<br>
On 06/06/2013 01:38, Deepali Khushraj wrote:<br>
</div>
<blockquote type="cite">
<div>* 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. . <br>
</div>
</blockquote>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
</div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
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 style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
</div>
</div>
</blockquote>
I forgot a to add this usecase. This can now be done in the
"Variants" tab.<br></div></blockquote><div><br></div><div>i was looking at this again and a question popped into my head. Doesn't each variant need there own certificate/google key. </div><div><br></div>
<div>So, for example, we have an "HR App", this app has 3 variants</div><div><span style="white-space:pre-wrap"> </span>1. free version</div><div><span style="white-space:pre-wrap"> </span>2. paid version</div>
<div><span style="white-space:pre-wrap"> </span>3. some other really cool version</div><div><br></div><div>i'm assuming that should be 3 different certs/keys ( for development, another set for prod ). i'm not sure the wireframes represent this correctly</div>
</div></div></blockquote><div><br></div><div><br></div><div>yes. the spec is indicating that!</div><div>Does the UI lead to confusion? <span></span></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </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"><div><div><br></div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
* Apple's Push network has prod and dev
environment options, a flag would be useful.</div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
</div>
</div>
</blockquote>
<br>
Two certificate files can now be provided: one for production and
one for development. Any of the two can be used by mobile apps
whether they're deployed or for debugging purposes.<br>
<br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<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><br>
</div>
</div>
</div>
</blockquote>
I've changed this to "Mobile Instances" for now, but we can discuss
this.<br>
<br>
<br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
* I found the name <span style="font-size:12px">"Variants and Push Networks"
confusing. I would suggest we use one :) </span></div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
</div>
</div>
</blockquote>
<br>
Push Networks it is.<br>
<br>
<blockquote type="cite">
<div>
<div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
* 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>
</blockquote>
I think this is something we need to fix on the <a href="http://aerogear.org" target="_blank">aerogear.org</a> website
itself. There should be easy access from the downloads to the API as
a "next step".<br>
<br>
<br>
<blockquote type="cite">
<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><br>
</div>
</div>
</blockquote>
<br>
<br>
<br>
<blockquote type="cite">
<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><span style="font-size:12px"><br>
</span></div>
</div>
</blockquote>
Like mentioned by Matthias, this can be anything, not just email
addressses. It depends on how the developer sets the system up.<br>
<br>
<blockquote type="cite">
<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</div></div></blockquote></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="javascript:_e({}, 'cvml', '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></blockquote>
</div><br></div></blockquote><br><br>-- <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><br>