So we’ve started a slack community for Maps UI/UX/Carto/DataViz. The group was born after organizing the UI/UX special interest group (SIG) meeting at 2017 Esri DevSummit in Palm Springs. 38 participants - partners, distributors, users – came not knowing what to expect but with questions that go beyond what Esri offers or teaches. So I thought: it takes a community to raise a child...
This slack community is a great place to:
- listen to our partners and users (be interested, not interesting)
- network and share with designers/developers from other mapping companies
- show our great work and cool stuff AND get instant feedback
- help others with their problems
Request an invite at http://www.designingmapinterfaces.com/patterns/join-maps-ui-ux-community-on-slack/ and feel free to forward to your buddies 😉
Please join https://maps-ui-ux-community.slack.com/ and participate. Hope to see you there...
Here the references mentioned during the talk "User Experience & Interface Design for Map Apps":
Map UI Patterns
UI Patterns & Best Practices for Map Applications
Demo: Durango Trail Finder
Calcite Maps Styler Template
A Bootstrap theme for designing, styling and creating modern map apps
MDL (Material Design Lite)
Canvas Flowmap Layer
Leaflet Migration Layer
Basemaps on ArcGIS
USA Media Basemap
I’m very pleased to announce that Ryan Watkins has joined our UI Engineering team at Esri.
Ryan earned his BS in Computer Science from University of California Riverside and attended the Art Institute in Los Angeles for Game Art & Design. His previous jobs equip him with an extensive background in front-end development (full stack) and hands-on experience in game design (unity).
Ryan is the author of the book "Procedural Content Generation for Unity Game Development"
He has a keen eye for application and graphics design and we are looking forward having him as integral part of the team, division and company. Welcome on board!
Let's start with a warming up exercise: Which of these 2 examples do you think is the best design? A, the airplane cockpit of an A380? Or B, the all-too-familiar Google interface?
This is the coolest thing I've seen in a long time. A real-time integrated augmented reality system to physically create topography models which are then scanned into a computer in real time, and used as background for a variety of graphics effects and simulations. #gottahave
More info about this project: http://idav.ucdavis.edu/~okreylos/ResDev/SARndbox/
Here the video for my talk about best practices for designing map applications on the web from Esri DevSummit 2015.
Every map application has two characteristics in common: it tries to solve a problem, and it needs a user interface (UI) to do so. This session presents best practices for solving well-known design problems and how to create easy-to-use and compelling interfaces. - See more at: http://video.esri.com/watch/4316/user-experience-and-interface-design-for-web-apps
This week Kevin (Yuan) Gao (LinkedIn) joined our team as a UI Engineer.
Kevin earned his Master of Science (MSc.) degree in Human Computer Interaction (HCI) from the University of Michigan. He also received a Bachelor of Business Administration (BBA) from the Shanghai Jiao Tong University.
I'm very happy that Kevin decided to join our team and am looking forward to seeing his HCI and design skills being applied to designing map interfaces for Esri Professional Services. Welcome on board!
Dashboards are everywhere, they can be found in business apps, management information systems, administration tools. They all have the following in common, they show summaries, key trends, comparisons, and exceptions. Usually all of above relate to key performance indicators or to derived (rolled up) data.
The "traditional" Dashboard
In the spatial space the data is rolled up to geographical (mostly political) units like continents, countries, or states and therefore provide a graphical presentation of the current status (temporal) in relation to its geographical location. This is typically displayed as a thematic map side by side with summaries, charts, gauges, graphics, or tables.
While this approach is completely valid its biggest weakness is the disconnect of visual perception to visual presentation of information, i.e. the intent of communicating geographical information isn't clear or at a minimum ambiguous. How do the data charts relate to the data shown on the map?