I get "mobile first", sure, but this new design is a mobile only design... The same way really old web sites are desktop only designs.. While desktop users might be in a decline, I like to believe they/we are still enough to care about?
The new design is simply bad on a big screen, why? Because it's a design for small screens... Different sized screens require different design layout, otherwise one will suffer. You don't need 10 different, that's a waste of energy to develop, but at least two, for desktop and mobile/tablet sized screens.
This is exactly the same thing that happened before "the mobile revolution", history repeating itself, but then it was "desktop only" sites that we bad on mobile but good on desktop. Going the other way around doing a design that is good on mobile and bad on desktop, being a company like Google, I think is just sad... I can get a small company that can't afford the engineering effort or that don't have the talent, but yeah, I think Google should have that, one good designer is all that is needed really at the base of it, and I think Google have plenty of great designers.
Note: post is a bit more specific, and I agree that it's the columns that is my biggest issue with the new design as well.
Please or or whoever else is responsible at Google, consider making the number of columns dynamic. It's easy to do a responsive grid... Just because some designer or project manager gets a nice feeling because it's 2 columns on all devices, thinking, "great consistent experience", that is not a good reason. It's logically consistent, sure, but it's bad for the desktop users in practice. It's still a consistent experience even if you change the grid to be dynamic/responsive, changing to a 2-3 or even 2-5 responsive column design (making the experience great for those with big high res monitors). While it's true that mobile is growing, it's also true that it's becoming more and more common with bigger screen for desktops, simply because of price. I think making the number of columns dynamic would make a huge difference, please consider this and take it up at some meeting.
And the "+1" functionally on comments, why force desktop users to double click?!? It's a terrible design, I think lots of people will simply stop "+1" on comments because of this... Please implement a "hover enabled single click +1" design, or some other single click design. Again you can enable this only on desktop and/or screens bigger than X*Y.
Don't let the users suffer just because it's a little bit easier for developers to have one single way of doing everything, a finger and a mouse pointer are very different, pressing the "+1" button that appears while hovering is a great user experience in the old design (using a mouse pointer). Don't force desktop users to use a weird double click finger optimized design, many users will simply stop using "+1" on comments and that is a terrible thing to happen for any type of social application, it simply lowers user engagement.
Design changes that lowers user engagement is bad for both Google and the Google plus users as a group.
#webdesign #webdevelopment #gplus #design
From an Apps users point of view (my company use G+ heavily) the new G+ is a disaster. It doesn't live-update, there are fewer posts available on screen, events are apparently gone and it is an utter pain to write private messages. It takes several clicks to not share a post with the entire organisation.
Not a single one of my employees like it. Not one.
If Google force this "update" on us, we will have to look elsewhere for a better tool. Heck, I might even consider leaving Google Apps completely, as this certainly makes me very nervous about what they will radically change next. Gmail? Drive? Calendar? Groups?
I run a business. I need to be able to trust that the tools we use are not massively changed from day to day.
Thanks for these great tools (and all others involved of course), keep 'em comin! :)
"Design and build full-featured web and CLI apps using the powerful Dart language and its libraries and tools"
Check it out at https://www.packtpub.com/web-development/dart-essentials
Check out the slides:
And the associated code lab:
Blog post about the event:
My two first installed apps so far is Spotify and Sky Demo, if people have any app tips feel free to add a comment.
I'm quite sure that an interpreted Dart VM like Fletch can never become as fast as the "normal" Dart VM, just because of how it's built. Therefor I think the Dart VM is not going anywhere, and Fletch will live alongside. There is a very clear reason/motivation to keep both, as long as Dart on mobile is successful that is (otherwise I think it's more likely that Fletch would be removed, but I think Dart on mobile will be successful and neither is removed). Remember that the primary reason for Fletch being interpreted is iOS dumb rules that prohibits running a JIT VM... I think Fletch the VM is primarily for iOS, only an interpreted VM can run there, whereas the concurrency concepts from Fletch as a project they come there first but will later propagate over to the normal Dart VM as well.
I don't remember 100% but I think I talked to or someone else at the Dart Summit about Fletch on the server, and I'm quite sure the plan is to port over the concurrency concepts that you are interested in over to the Dart VM, and then you can get both high performance and a potentially better concurrency model. That's why I guess i got a bit hang up on the "Fletch on the server for performance" part, because I don't think that is going to happen.
Basically what I'm saying is that the project "Fletch" contains two new things, an interpreted VM and new concurrency concepts. When I read Fletch I think of the VM primarily, because that is the main part of the project I think. And yeah, I quite sure that if the new concurrency model is found to be beneficial that will be ported over to the Dart VM as well.
You can try it by pressing on "Compact list view" in the little menu on the right of the "About" button in the upper right corner.
1. An explanation of the new and "up-and-coming" Dart feature called null-aware operators (with examples) by .
2. Material design light for Dart has been released, as easy to use as Bootstrap or PureCSS but with beautiful Material Design elements. The effort to create a Dart implementation of MDL has been lead and implemented by , great work Mike!
3. A new template-base project generator, also by .
4. For a bigger picture understanding of what MDL is, see this blog post introducing the new library.
5. Looking at MDL you will see that the CSS uses double underscore ("__") and double hyphens ("--") in various places. This is because the CSS styles are written using a "style" called BEM. BEM simply aims to bring structure to how you name your CSS classes. I found this article on BEM very helpful understanding the why and how BEM works.
Go, go, go!
- DartVoidFounder, Chief Software Architect and Developer, 2012 - present
- RemroCEO and Computer Engineer, 2011 - present
- Umeå UniversityStudent, Elite Athlete, 2008 - present
- SAS StomzRadio Technician, 2006 - 2011
- University of Umeåpresent
- Bergs Gymnasium
Could Server-Side Dart Replace Node.js? | CenturyLink Labs
Dart is a Google-produced programming language that has slowly been gaining traction, particularly since its 1.0 release last year. While Da
Chromium Blog: Ecma forms TC52 for Dart Standardization
This week Ecma created a new technical committee named TC52 to publish a standard specification of the Dart language. We're excited about th
Top 5 Live Websites Already Using The Dart Language
The Dart is still heading towards that magical 1.0 release but that is not stopping pioneering developers using the language. It is not just