Thanks guys, this clears up a lot about what we want to cover and can do.
I'll make some proposals that we can discuss on Friday.
Hylke
On 14/05/2014 08:59, Matthias Wessendorf wrote:
On Tue, May 13, 2014 at 10:47 AM, Hylke Bons <hbons(a)redhat.com
<mailto:hbons@redhat.com>> wrote:
Hello,
Depending on the use case, it may even deserve its own spot in the
sidebar. Like already mentioned on the thread, it's better to keep
the number of items there fixed. We may have have several entry
points to the logs, and an overview of some statistics can be
useful as a landing page before going into "Applications".
Let's step back for a moment before looking at the UI: What are we
trying to solve by providing a log?
- Let administrators know everything is going well? (or, that
there was a problem?)
yes, see the data I mentioned earlier in the thread
- Looking at resources used? Bandwidth, costs?
Nope
- App adoption/growth numbers over time? How well is my app doing?
Nope
I'm not sure about the technical possibilities. Thoughts?
yeah, the nopes are not possible :)
Thanks,
Hylke
On 07/05/2014 10:54, Matthias Wessendorf wrote:
> Hi,
>
> as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
>
>
> But, where, or how to add this ?
> My current thought is:
>
> When a user did select an "Application", he enters the
> "Application Details Page" (see [1]), now here, on the sidebar
> (see [2]) he would see the "Notifications" icon.
>
> Clicking on that "Notifications" icon, would give you a new
> page, that contains the "Send Notifications..." button (currently
> located in [1]), and a table of all the push messages that were
> sent out for the _current_ selected Application.
>
> Any thoughts ?
>
> -Matthias
>
> [1]
>
https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Ser...
> [2]
>
https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Ser...
>
>
> --
> 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 <mailto:aerogear-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@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