[aerogear-dev] Progress on Unified Push Server UI

[Hylke Bons]

On 03/06/2013 18:11, Daniel Bevenius wrote:
> Hi Hylke,
>
> Nice work! I like the look of the Admin UI
>
Thanks Daniel!

> >- Using "(Hybrid Web)" as a variant name instead of "SimplePush".
> I'd vote for changing "Hybrid Web" to just "Web". For me the UI is 
> pretty clear that this is about adding/configuring Push Networks, and 
> I would not know what a "Hybrid Web" push network is.
>
> /Dan
>
Yes, I tend to agree. Perhaps we can add a short description of what 
"Web" entails (Cordova, "plain" web etc.). Compared to the other 
platforms, this may not be immediately clear from the beginning. 
Something to think about.

Thanks,

Hylke

>
> On 3 June 2013 17:31, Hylke Bons <hbons at redhat.com 
> <mailto:hbons at redhat.com>> wrote:
>
>     Hey everyone,
>
>     Here's my initial version of the AeroGeer Unified Push Server
>     Admin UI:
>     https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push_server_admin_ui.png
>
>     This work is based off of the features/usecases and lexicon
>     described in http://aerogear.org/docs/specs/aerogear-server-push/
>     and Matthias's earlier wireframes.
>
>
>     Features:
>
>       * Developer can register a |Push Application|
>       * Developer can add a |Mobile Variant| for different operation
>         systems
>       * Developer can remove a |Mobile Variant|
>       * Developer can remove |Push Application|
>
>     Currently Missing features (these will be added in the next
>     iteration):
>
>       * Enroll |Developer|
>       * Remove |Developer|
>       * |Developer| can disable Push Notifications to selected |Mobile
>         Variant Instances|
>       * |Developer| sends /Push Notification Messages/
>
>
>     Potentially controversial changes:
>
>       - Using "(Hybrid Web)" as a variant name instead of
>     "SimplePush". Matthias and I already had a short exchange here on
>     the mailing list about this change, hopefully the way this is used
>     in these wireframes will shed some light on why I think this is a
>     better choice.
>       - Checkboxes instead of a list box for variants. Since there are
>     only a few variant types, we don't need a full fledged list, and
>     we can simply use some checkboxes to toggle variants.
>
>     Let me know if you have any comments or questions!
>     Sources can be found in https://github.com/hbons/aerogear-design.
>
>     Looking forward to your feedback,
>
>     Hylke
>
>
>
>     _______________________________________________
>     aerogear-dev mailing list
>     aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130603/580314b4/attachment.html