<div dir="ltr">+1 on 4a and 4b</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 16, 2015 at 3:36 PM, Andres Galante <span dir="ltr"><<a href="mailto:agalante@redhat.com" target="_blank">agalante@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is the wizard flow, please check if we can do it:<br>
<br>
1- Creates the app<br>
<a href="http://andresgalante.com/ups-console/wizard01.html" target="_blank">http://andresgalante.com/ups-console/wizard01.html</a><br>
<br>
2- Creates the variant (we validate this form before moving forward)<br>
<a href="http://andresgalante.com/ups-console/wizard02.html" target="_blank">http://andresgalante.com/ups-console/wizard02.html</a><br>
<br>
3- Information on how to set up the variant. We need to write very good instructions:<br>
<a href="http://andresgalante.com/ups-console/wizard03.html" target="_blank">http://andresgalante.com/ups-console/wizard03.html</a><br>
<br>
4 a- IF we have one installation we let him send the notification:<br>
<a href="http://andresgalante.com/ups-console/wizard04.html" target="_blank">http://andresgalante.com/ups-console/wizard04.html</a><br>
<br>
4 b- IF we have NO installations we give the user the option to skip this step or go back and get instruction to set up his device:<br>
<a href="http://andresgalante.com/ups-console/wizard04-alt.html" target="_blank">http://andresgalante.com/ups-console/wizard04-alt.html</a><br>
<br>
5- set up sender API.....<br>
<br>
I also added links to edit variant info or app name.<br>
<br>
What do you think?<br>
<span class="im HOEnZb"><br>
<br>
----- Original Message -----<br>
From: "Matthias Wessendorf" <<a href="mailto:matzew@apache.org">matzew@apache.org</a>><br>
To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
</span><div class="HOEnZb"><div class="h5">Sent: Friday, January 16, 2015 9:47:57 AM<br>
Subject: Re: [aerogear-dev] UPS console redesign screencast and demo<br>
<br>
<br>
<br>
On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante < <a href="mailto:agalante@redhat.com">agalante@redhat.com</a> > wrote:<br>
<br>
<br>
Good morning!<br>
<br>
I added tabs on the code snippet (click on the one that has no installations):<br>
<a href="http://andresgalante.com/ups-console/app-detail-variants.html" target="_blank">http://andresgalante.com/ups-console/app-detail-variants.html</a><br>
<br>
and sub menu for node.js or other Sender API:<br>
<a href="http://andresgalante.com/ups-console/app-detail.html" target="_blank">http://andresgalante.com/ups-console/app-detail.html</a><br>
<br>
<br>
good stuff!<br>
<br>
<br>
As for step 2 and 3 of the wizard I still working on different flow options. I'll share with you something today to continue the discussion.<br>
<br>
cool! looking forward to that :-)<br>
<br>
<br>
<br>
Thanks<br>
<br>
----- Original Message -----<br>
From: "Matthias Wessendorf" < <a href="mailto:matzew@apache.org">matzew@apache.org</a> ><br>
To: "AeroGear Developer Mailing List" < <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> ><br>
Sent: Thursday, January 15, 2015 3:15:12 PM<br>
Subject: Re: [aerogear-dev] UPS console redesign screencast and demo<br>
<br>
<br>
<br>
On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> > wrote:<br>
<br>
<br>
<br>
<br>
<br>
On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> > wrote:<br>
<br>
<br>
<br>
<br>
<br>
On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> > wrote:<br>
<br>
<br>
<br>
<br>
<br>
On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < <a href="mailto:matzew@apache.org">matzew@apache.org</a> > wrote:<br>
<br>
<br>
<br>
Hin Andres!<br>
<br>
Wow! awesome - I love it! Where can I sign? :-)<br>
<br>
<br>
I watched the excelent video and here are a few coments on the new UI<br>
<br>
<br>
*Wizzard*<br>
<br>
After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI.<br>
<br>
Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-)<br>
Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious<br>
I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check.<br>
<br>
well, not much will happen:<br>
<a href="https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59</a><br>
Ah right :) Because there are no installation but beside that "implementation issue" , would be nice to have a way to test if the API Key etc ... are valid .<br>
<br>
I agree - we can change it, I think we even have a ticket for that already<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next)<br>
<br>
You mean present the "Send dialog" only if there is at least one device already registered? Otherwise, we can again state: now it's time to get a device registered... or something like that - not sure<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
"Applications overview"<br>
<br>
wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location.<br>
<br>
<br>
"App and its Variants overview"<br>
-> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong<br>
-> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic<br>
<br>
<br>
<br>
"Sender API"<br>
We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code)<br>
<br>
I do really like the INFO _above_ the code. All info in one place - good stuff<br>
<br>
<br>
"Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet!<br>
<br>
<br>
<br>
Skip Wizzard -> nice, overview with the blank screens<br>
<br>
<br>
Again, awesome work - I am really looking to get this implemented<br>
<br>
<br>
<br>
On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < <a href="mailto:agalante@redhat.com">agalante@redhat.com</a> > wrote:<br>
<br>
<br>
Hi,<br>
<br>
I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :)<br>
<br>
Here is a screencast walk through:<br>
<a href="http://youtu.be/-ab4-F4OCJM" target="_blank">http://youtu.be/-ab4-F4OCJM</a><br>
<br>
And here is the prototype for you to click around:<br>
<a href="http://andresgalante.com/ups-console/wizard01.html" target="_blank">http://andresgalante.com/ups-console/wizard01.html</a><br>
<br>
<br>
There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible.<br>
<br>
Please take a close look and try to find holes in the interaction. Let me know what you think.<br>
<br>
Thanks!<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>
<br>
<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>
<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>
<br>
<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>
<br>
<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>
<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>
<br>
<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>
<br>
<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>
<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>
_______________________________________________<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>
<br>
<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>
<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>
_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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>