<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 21/06/2013 16:07, Lucas Holmquist
wrote:<br>
</div>
<blockquote
cite="mid:859FA317-724C-4CE5-B8A6-211E87A68594@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
also, do we need a background image on the login page, or will
this be on all pages<br>
<div>
<div>On Jun 21, 2013, at 10:38 AM, Lucas Holmquist <<a
moz-do-not-send="true" href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
</div>
</blockquote>
<br>
It's just there because it looks nice and it's a theme. :)<br>
It will just be on the login page, not anywhere else. Although we
could make it shine through a little bit in the page header.<br>
<br>
Hylke<br>
<br>
<br>
<blockquote
cite="mid:859FA317-724C-4CE5-B8A6-211E87A68594@redhat.com"
type="cite">
<div>
<blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">design is looking
good.
<div><br>
</div>
<div>Some Comments:</div>
<div><br>
</div>
<div>On the First screen after login( and subsequent detail
pages ), i would probably remove the "View Details" button
and just make the value in the Name column clickable.
Probably makes sense to remove the "Remove" button too
and put a "delete" icon or something next to the name of
the app</div>
<div><br>
</div>
<div>either that or when a row is clicked, those button(s)
appear. More of an implementation detail really</div>
<div><br>
</div>
<div>
<div>
<div>On Jun 17, 2013, at 8:19 AM, Hylke Bons <<a
moz-do-not-send="true"
href="mailto:hbons@redhat.com">hbons@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello,<br>
<br>
I've updated the wireframes with the points
raised, you can find it here:
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push_server_admin_ui.png">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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">* 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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<div style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "><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; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">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; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "><br>
</div>
</div>
</blockquote>
I forgot a to add this usecase. This can now be done
in the "Variants" tab.<br>
<br>
<blockquote
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<div style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">*
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; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "><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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<div style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">
<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
class="Apple-tab-span"
style="white-space:pre"> </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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<div style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">* 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; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "><br>
</div>
</div>
</blockquote>
<br>
Push Networks it is.<br>
<br>
<blockquote
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<div style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; ">* 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
moz-do-not-send="true" href="http://aerogear.org/">aerogear.org</a>
website itself. There should be easy access from the
downloads to the API as a "next step".<br>
<br>
<br>
<blockquote
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<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
cite="mid:582FA9AB-B6C3-47B9-AB97-B551770212B9@redhat.com"
type="cite">
<div apple-content-edited="true">
<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>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div>
<br>
</div>
</div>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</body>
</html>