- Using "(Hybrid Web)" as a variant name instead of "SimplePush".

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... 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

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(a)redhat.com&gt; 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... > > 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing listaerogear-dev@lists.jboss.orghttps://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

On 03/06/2013 18:45, Matthias Wessendorf wrote: > I would treat Cordova native: > -Cordova-Android-Variant > -Cordova-iOS-Variant > > Of course, with SimplePush, the apps can receive notifications as > well, but the "background" (not actively running), would not be > possible (at least now) > > -Matthias > So do Cordova hybrid based apps use their respective "native" push networks (Apple's/Google's) SimplePush only? (or either?) I guess non-hybrid Web apps can only use SimplePush?

Hylke _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

So do Cordova hybrid based apps use their respective "native" push networks (Apple's/Google's) SimplePush only? (or either?) I guess non-hybrid Web apps can only use SimplePush? I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova variants. You can use our SimplePush libraries, with Cordova. But.... you would NOT receive a notification, if the application is not running/open SimplePush is perfect, right now, for "Mobile Web", and would be fine for Cordova, where we do (yet) support the native bindings (e.g. BlackBerry, Windoze etc) -Matthias

On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com&gt; wrote: > On 03/06/2013 18:59, Matthias Wessendorf wrote: > > So do Cordova hybrid based apps use their respective "native" push >> networks (Apple's/Google's) SimplePush only? (or either?) I guess >> non-hybrid Web apps can only use SimplePush? >> > > I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova > variants. > > You can use our SimplePush libraries, with Cordova. But.... you would > NOT receive a notification, if the application is not running/open > > > SimplePush is perfect, right now, for "Mobile Web", and would be fine > for Cordova, where we do (yet) support the native bindings (e.g. > BlackBerry, Windoze etc) > > -Matthias > > > Thanks, that makes sense. > > I'll keep this in mind for the next iteration and think about how we want > to represent Cordova in these categories (if at all, perhaps it's a client > implementation detail). > yeah, I'd probably not even mention Cordova in the UI; In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush). > > > Hylke > > _______________________________________________ > 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

For the admin UI, do we have a browser(s) target. If this is possibly going to be a "module" in AS , then developers in certain enterprises might be stuck using old versions of IE( < than 9 )

On Jun 4, 2013, at 2:32 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Hello Hylke, > > here is the "Admin UI" epic (incl. its sub-tasks): > https://issues.jboss.org/browse/AGPUSH-66 > > can you update, e.g. assign issues to yourself, add new one, modify existing tickets, as needed ? > > Thanks! > Matthias > > > > > On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com&gt; wrote: > On 03/06/2013 18:59, Matthias Wessendorf wrote: > >> So do Cordova hybrid based apps use their respective "native" push >> networks (Apple's/Google's) SimplePush only? (or either?) I guess >> non-hybrid Web apps can only use SimplePush? >> >> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova variants. >> >> You can use our SimplePush libraries, with Cordova. But.... you would NOT receive a notification, if the application is not running/open >> >> >> SimplePush is perfect, right now, for "Mobile Web", and would be fine for Cordova, where we do (yet) support the native bindings (e.g. BlackBerry, Windoze etc) >> >> -Matthias >> > > Thanks, that makes sense. > > I'll keep this in mind for the next iteration and think about how we want to represent Cordova in these categories (if at all, perhaps it's a client implementation detail). > > yeah, I'd probably not even mention Cordova in the UI; > In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush). > > > > > Hylke > > _______________________________________________ > 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 > > > > -- > 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

PLUS PLUS On Tue, Jun 4, 2013 at 2:49 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: On Jun 4, 2013, at 7:16 AM, Lucas Holmquist <lholmqui(a)redhat.com&gt; wrote: > For the admin UI, do we have a browser(s) target. If this is possibly going to be a "module" in AS , then developers in certain enterprises might be stuck using old versions of IE( < than 9 ) Well, AeroGear doesn't support IE < 9 so ... > > > > > On Jun 4, 2013, at 2:32 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > >> Hello Hylke, >> >> here is the "Admin UI" epic (incl. its sub-tasks): >> https://issues.jboss.org/browse/AGPUSH-66 >> >> can you update, e.g. assign issues to yourself, add new one, modify existing tickets, as needed ? >> >> Thanks! >> Matthias >> >> >> >> >> On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >> >> >> On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com&gt; wrote: >> On 03/06/2013 18:59, Matthias Wessendorf wrote: >> >>> So do Cordova hybrid based apps use their respective "native" push >>> networks (Apple's/Google's) SimplePush only? (or either?) I guess >>> non-hybrid Web apps can only use SimplePush? >>> >>> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova variants. >>> >>> You can use our SimplePush libraries, with Cordova. But.... you would NOT receive a notification, if the application is not running/open >>> >>> >>> SimplePush is perfect, right now, for "Mobile Web", and would be fine for Cordova, where we do (yet) support the native bindings (e.g. BlackBerry, Windoze etc) >>> >>> -Matthias >>> >> >> Thanks, that makes sense. >> >> I'll keep this in mind for the next iteration and think about how we want to represent Cordova in these categories (if at all, perhaps it's a client implementation detail). >> >> yeah, I'd probably not even mention Cordova in the UI; >> In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush). >> >> >> >> >> Hylke >> >> _______________________________________________ >> 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 >> >> >> >> -- >> 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 _______________________________________________ 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

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... 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

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... 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev