[aerogear-dev] First go at stats/activity wireframes

[Burr Sutter]

Not that you asked me but :-)

+1 on the horizontal "dashboard" section
+1 to the concern related to "status" - the first time I saw it I felt it only addressed errors - not all possible but recent "activity"
I think the word "Log" or "Activity" would be better

On May 21, 2014, at 8:45 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> Hylke,
> 
> any comments on Matt's reply?
> 
> Or is this the final draft:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> 
> -Matthias
> 
> 
> 
> On Mon, May 19, 2014 at 5:48 PM, Matt Carrano <mcarrano at redhat.com> wrote:
> Hey Hylke,
> 
> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
> 
> -Matt
> 
> ----- Original Message -----
> From: "Hylke Bons" <hbons at redhat.com>
> To: aerogear-dev at lists.jboss.org
> Cc: "Matt Carrano" <mcarrano at redhat.com>
> Sent: Monday, May 19, 2014 8:03:13 AM
> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
> 
> Hello,
> 
> Here are some updates based on the feedback from the meetings:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> - Simplified dashboard stats
> - Apps notifications table
> - Defined entry points
> 
> Let me know what you think. I hope that covers everything.
> 
> Thanks,
> 
> Hylke
> 
> 
> 
> On 15/05/2014 16:19, Hylke Bons wrote:
> > Hey,
> >
> > Here's an initial version:
> > https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > I tried to incorporate most wishes expressed in the other thread.
> >
> > Most notable things:
> > - Landing page with an overview of stats, most active apps, and error
> > messages
> > - Activity table shows both registration and notification events
> > - Activity table is per variant, and not all activity on the server.
> > Unless there's a usecase to have every event for every app/variant in a
> > table I don't think we actually need it. The important thing is to get
> > to error messages easily.
> >
> > Things to do/think about:
> > - links/entry points to the activity table
> > - filtering the activity table
> >
> > This is just the first iteration and we will improve on this.
> > Let me know what you think.
> >
> > Thanks,
> >
> > Hylke
> > _______________________________________________
> > aerogear-dev mailing list
> > 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
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> 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/20140521/3250fd4f/attachment.html