On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>
>
> On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> wrote:
>
>>
>>
>> On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf <matzew(a)apache.org>
>> wrote:
>>
>>> Hin Andres!
>>>
>>> Wow! awesome - I love it! Where can I sign? :-)
>>>
>>>
>>> I watched the excelent video and here are a few coments on the new UI
>>>
>>>
>>> *Wizzard*
>>>
>>> After "Mobile device: Setup variant", when clicking
"Continue", it
>>> brings us to the "test push" UI.
>>>
>>> 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 :-)
>>> Perhaps we should bake that SKIP option a bit into the TEXT - so that
>>> it is obvious
>>>
>> 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.
>>
>
> well, not much will happen:
>
>
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/...
>
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 .
I agree - we can change it, I think we even have a ticket for that already
>
>
>>
>> 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)
>>
>
> 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
>
>
>>
>>>
>>> "Applications overview"
>>>
>>> wow -> that looks great :) Glad the navigation bar is gone - you are
>>> right -> way better. I also like the dashboard location.
>>>
>>>
>>> "App and its Variants overview"
>>> -> with no installations: not sure we do always, in that case,
>>> immediately show the source code. But I can be wrong
>>> -> with installations: let's integrate pagination. e.g. 10 per page!
>>> the table looks fantastic
>>>
>>>
>>>
>>> "Sender API"
>>> 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)
>>>
>>> I do really like the INFO _above_ the code. All info in one place -
>>> good stuff
>>>
>>>
>>> "Send Notification to App" I like the popup/dialog, including the
>>> disabled button when there are no devices. Sweet!
>>>
>>>
>>>
>>> Skip Wizzard -> nice, overview with the blank screens
>>>
>>>
>>> Again, awesome work - I am really looking to get this implemented
>>>
>>>
>>>
>>> On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante <agalante(a)redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I've been working on UPS console redesign for the last couple of
weeks
>>>> and I am finally able to share it with you :)
>>>>
>>>> Here is a screencast walk through:
>>>>
http://youtu.be/-ab4-F4OCJM
>>>>
>>>> And here is the prototype for you to click around:
>>>>
http://andresgalante.com/ups-console/wizard01.html
>>>>
>>>>
>>>> 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.
>>>>
>>>> Please take a close look and try to find holes in the interaction. Let
>>>> me know what you think.
>>>>
>>>> Thanks!
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog:
http://matthiaswessendorf.wordpress.com/
>>> sessions:
http://www.slideshare.net/mwessendorf
>>> twitter:
http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf