<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 21, 2013 at 5:38 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div><div class="im"><div>On Jun 21, 2013, at 11:23 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 21, 2013 at 5:16 PM, 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"><div style="word-wrap:break-word">Just saw this email. The updates look good. <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">
<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">
Matthias, also one question to you: can a single variant have multiple push networks (APNS, GCM etc) associated with it? All the examples in the spec have only a single push network associated with a "variant", so that part was not clear. </div>
</div></div></div></blockquote><div><br></div><div>The idea is:</div><div>PushApp: Overall mobile App (e.g. "AeroGear Sports News").</div><div>Variant: A _variation_ of this (for a specific target). "AeroGear Sports News for iOS", "AeroGear Sports News for Android" or "AeroGear Sports News for Web".</div>
<div><br></div><div>Now... with a bit more "fine tuning" (e.g. the the user/company wants to be fancy and offer specific apps (to the app-store) for iPhone/iPad or Android Tablets/Phones"), these following "variants" could exist for the "AeroGear Sports News" Push Application:</div>
<div><div>* "AeroGear Sports News for iPhone"<br></div><div>* "AeroGear Sports News for iPad"<br></div><div>* "AeroGear Sports News for iPad mini"<br></div><div>
* "AeroGear Sports News for Android-Table"<br></div><div>* "AeroGear Sports News for Google-Glasses"<br></div><div><br></div></div><div>Since a variant targets a specific platform, there is no real sense in having the one variant supporting different PushNetworks. thins like that are group under a PushApplication (as explained above).</div>
<div><br></div><div><br></div><div>Does that make sense? Do you feel I need to be more clear on that in the spec ? </div></div></div></div></blockquote><div><br></div></div><div>Your approach sounds reasonable. Perhaps just a line in the spec, explicitly stating this, could be useful. </div>
<div><br></div><div>Do you plan to allow the user to configure both dev and prod certificates of APNS for a single iOS variant?</div></div></div></blockquote><div><br></div><div><br></div><div style>yes. And I think Hylke's wireframes already indicate that </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><div class="h5"><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div><br></div><div><br></div><div>-Matthias</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><span><font color="#888888"><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>D.
</font></span></div>
<br><div><div><div><div>On Jun 17, 2013, at 8:19 AM, Hylke Bons <<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>> wrote:</div><br></div></div><blockquote type="cite"><div><div>
<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>
<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
apps' "beta testing" though.</div>
<div><br>
</div>
</div>
</blockquote>
It can be a long list and we probably will have to add pagination
and filtering. The main usecase here is removing instances to stop
them from receiving new push notifications.<br>
<br>
<blockquote type="cite">
<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><br>
</div>
</div>
</blockquote>
<br>
It was to to select applications and perform actions on them. I
already thought this would be confusing, so I removed them now. An
app is active when it has at least one push network enabled.<br>
<br>
<br>
<blockquote type="cite">
<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>
</blockquote>
<br>
Yep, potentially.<br>
<br>
<blockquote type="cite">
<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>
<br>
</div>
</blockquote>
Yes, I've added some paragraphs to make things more friendlier, but
there's room for improvement. We can fix this as we go.<br>
<br>
Thanks for the feedback. It's been really useful!<br>
<br>
Hylke<br>
<br>
</div></div></div><div>
_______________________________________________<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></div>
</blockquote></div><br></div></div><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><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" 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></div></div><br></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>