Donhkoland is the result of an enormous variety of influences from projects of either big or small enterprise; where every process turns out to be a trip to find the essence of a great design.
Yesterday saw me back in our Campfire chatroom, this time with insights and innovation expert Steve Portigal.
We were talking about a subject that I found very interesting – using insights to inform design decisions and innovation. We spend a lot of time talking about how and why to conduct user research, but very little time talking about the specifics of applying the things that we learn from that research.
Steve is Principal of portigal.com – a consultancy which specialises in helping companies discover and act on new insights about their customers and themselves. He is also the author of Interviewing Users: How to Uncover Compelling Insights.
It was a busy session, but Steve absolutely nailed it. A lot of handy resources came out of it, and I’ve listed them below so that you don’t have to sift through the transcript to find them.
When to Use Which User-Experience Research Methods Christian Rohrer
Championing Contextual Research in your Organization Steve Portigal
Well, We’ve Done All This Research, Now What? Steve Portigal
Fons Trompenaars’ Global Cultures Model
Steve’s obligatory Star Wars reference Kobayashi Maru
Dollars to Donuts Steve’s podcast (with transcripts)
If you didn’t make the session because you didn’t know about it, make sure you join our community to get updates of upcoming sessions. If you’re interested in seeing what we discussed, or you want to revisit your own questions, here is a full transcript of the chat.
|
Twitter
Google+
The post Transcript: Ask the UXperts:Using Insights to Inform Design & Innovation—with Steve Portigal appeared first on UX Mastery .  by Sarah Hawk via UX Mastery |
As a JavaScript developer, I’m sure you’ve already been falling into this scenario: something goes wrong with the production version of your code, and debugging it directly from the production server is a nightmare simply because it has been minified or has been compiled from another language such as TypeScript or CoffeeScript.
The good news? The latest versions of browsers can help you solve this problem by using source map. In this tutorial, I’ll show you how to find Source Maps in all of the browsers and get the most out of those few minutes you have to debug.
According to the great Introduction to JavaScript Source Maps article, source map is “a way to map a combined/minified file back to an unbuilt state. When you build for production, along with minifying and combining your JavaScript files, you generate a source map which holds information about your original files”.
Please don’t hesitate to read Ryan Seddon’s article first as it goes in great details on how source map works. You’ll then learn that source map uses an intermediate file that does the matching between the production version of your code and its original development state. The format of this file is being described here: Source Map Revision 3 Proposal
Now to illustrate, I’m going to share the way we’re currently working while developing our WebGL Babylon.js open-source framework: http://ift.tt/1aUDteS. It’s written in TypeScript. But the principles will remain the same if you’re using plain JavaScript compressed/minified or other languages such as CoffeeScript.
Let’s now play with the source map magic directly in the browsers.
Recently, I’ve been implementing the support of the Gamepad API in our gaming engine. Let’s use its code for this tutorial.
In this article, I’m using the following browsers:
Navigate to this URL: http://ift.tt/1EUSJc5 and you’ll see this page:
Plug an Xbox 360 or Xbox One controller in the USB port of your machine. Press the A button to activate the gamepad and play with it:
But don’t worry, you won’t need a gamepad controller to follow this tutorial.
Note: The TypeScript compiler is automatically generating the source map for you. If you’d like to generate a source map while generating your minified version of your code, I would recommend using Uglify JS 2: http://ift.tt/MWUf1D
For this article, I even mixed both. I’ve minified the JS generated by TypeScript and kept the source mapping intact using this command line:
uglifyjs testgamepad.js -o testgamepad.min.js --source-map testgamepad.min.js.map --in-source-map testgamepad.js.map
Once the gamepad test page has loaded, press F12 in IE11.
You’ll see that the HTML source is referencing 2 JavaScript files: babylon.gamepads.js at the beginning of the page & testgamepad.min.js at the very end. The first file is coming from our framework on Github and the second one a simple sample showing how to consume it.
Continue reading %Enhance Your JavaScript Debugging with Cross-Browser Source Maps%
I was quite surprised when Microsoft announced that Internet Explorer — the Microsoft browser that has been around for nearly two decades — was going to be replaced by a browser then code-named Project Spartan (the browser’s final name, Microsoft Edge, was just revealed, so I’ll use that name for the rest of the article). […]
Continue reading %Microsoft Edge: A Hands-on Preview%
Maps have become an integral part of our daily lives. They provide directions, help us plan trips, find establishments, visualize data trends and share experiences. Using a map on your website is a great way to help visitors find your business, and provide relevant information based on a user’s location. You can also create applications that present your content in a manner that keeps visitors engaged and coming back to your site.
In this lesson, Robert will walk you through how to setup and configure your first map using the Google Maps API. The lesson includes sample code, so you'll be able to take what you've learned and start creating a map to include in your website. This is a sample lesson from the Learnable course Introduction to Google Maps API available now. As part of the course, we will be creating an interactive visualization to help you apply what you've learned.
Continue reading %Your First Google Map%
A secondary content panel that folds flat, powered by CSS Transformations and jQuery.
