User Experience

Advice for the next generation of entrepreneurs…

What do you say to the finalist teams in this year’s Apps for Good Awards? Not much really. They have all crafted an idea for an app that showcases their abilities to use technology to solve real life problems.  And in doing so they’ve gone on an amazing journey that has seen them demonstrate their understanding of the target audience and mobile technology, through to communicating their value proposition and how to monetize their app. All pretty impressive stuff. Even more impressive given the brains behind these innovations are from primary and secondary schools. So all that was left for me to discuss with 5 of the finalists last week, was how to pack the most punch in to their elevator pitch by guiding them on how to tell a compelling story in just 60 seconds.   Hopefully they took away some useful pointers.

What follows are some of the tips I shared with them… (the examples below all reference the team’s ideas and apps that have been shortlisted for the finals).

Help your audience to visualise the story you are telling

You have literally seconds to paint a picture. Yes, a picture says a thousand words, but some carefully chosen words can paint a pretty powerful picture. You’re not painting a Monet, but just enough for the audience to quickly visualise the opening scene of the story you are telling. So as you introduce the main character (persona) and set the scene, try to imagine the picture you are painting for your audience. Consider how changing something as simple as “Laura is learning to play an instrument” to “Laura is learning to play the piano” helps the listener to visualise it.

Create the drama

You’ve set the scene. Now you need to get your hooks in and create a bit of drama. This is where you communicate the problem you are solving.  Imagine you are delivering an Eastenders style cliffhanger – it needs that level of impact.  For example, “Our app will help make a huge impact on Sandra’s children’s lifelong relationship with food by encouraging healthy eating habits.” You can almost hear the drum roll…

Drop some big numbers

You have set the scene and delivered the drama. At this point the audience is most probably nodding their heads, “yes, seems like a good idea.”  Now you need to land a jaw-dropper. Go for the kill by dropping a large number that puts in to perspective the potential your idea has to really make a difference.   For example, “Ten percent (10%) of the British population are dyslexic.” Boom! Of course, make sure the numbers are accurate!

How will your idea solve the issue

A good story has a resolution.  You have a character, a setting and plot, have built some tension (with your big numbers) … now you need the resolution. This is a one-liner of epic proportions.  This is not what your idea will do, but how your idea will do it.  The difference is in the detail.   For example, go from “our app will help children with dyslexia to plan their day…” to “the app will provide tools, that puts the user in control, allowing them to plan and manage all aspects of their daily routine.”

There will most likely already be apps competing in your space.  With so many apps being created daily, it’s difficult to find a problem that someone isn’t already trying to tackle, regardless of whether they’re doing it well or not.  But it’s not always about being the first.  It’s about having that x-factor, a certain something that gives you the nod over the others.  A good way to set out what sets your app apart from the others is to complete this sentence, “our app beats the socks off the rest by ….”

How are you going to drive app engagement?

About 22-25% of apps are downloaded and used only once. What is it that will make your app get a return visit? Make sure you communicate why your users will keep coming back to use your app.

For example, “Our users don’t want to miss out on the latest hair style trends. They’ll come back to stay on top of the latest trends, comment on latest styles, and get advice from their friends before their next visit to the hairdressers…”  This helps to communicate how your app has a real sense of stickiness.

Make your app easy to use

There is a growing culture of impatience.  The ‘Impatient Nation’ demand instant gratification.  Apps therefore need a high convenience quotient.  What does all this mean? Well, if your mobile app doesn’t allow your user to quickly and easily achieve their goal then you risk losing them.   But saying your app is simple and easy to use isn’t quite enough!  This goes back to the first point about helping the listener to visualise your idea.

For example, “All Daniel needs to do his select guitar, and pluck the bottom-E string. Within seconds Daniel receives advice to turn the tuning key for the bottom-E string…”   This is a powerful way to help your audience to understand not only how your app works, but how easy it is to use.

Talk the talk

You’ve designed a mobile app, so make sure you use language that helps the audience to further visualise your app being used. Drop in references to mobile gestures such as pinch, zoom and swipe or discuss what happens when you rotate your phone. And highlight any features of the smartphone that your app uses such as the camera or GPS. As well as helping the audience to be further immersed, this also demonstrates your understanding of the mobile environment.

Make your app enjoyable to use

An app that is useful isn’t enough. It also needs to be usable. And still that’s not enough. We’re emotional people that like to be engaged.  Apps need to be delightful to use too, so help the audience to understand how your app delivers an emotional punch.  You can achieve this by providing engaging content and functionality, focusing on aesthetics, or incorporating elements of game design. So don’t focus purely on your apps functionality, but just as importantly communicate how users will be ‘engaged’ by your app.

Games are inherently more engaging, and reward mechanisms are a powerful gaming mechanism. If you are using such reward mechanisms to encourage users to eat their greens, or provide badges or other indictor of progress for say tuning your guitar in your fastest time, then get these powerful mechanics across when you present your idea.

Make sure your story flows

Everything you have covered until now needs to flow.  Good flow is one of the most important elements of good storytelling. Good flow minimises the cognitive effort to breakdown the information, by just adding layer upon layer to the original picture you helped to visualise.  If the flow stalls or stutters then the visual image starts to fade. You need to keep the flow and keep the listener engaged throughout…

There’s my pennies worth.  Now that’s all left for me to do is congratulate the finalists and wish them all the best for next week’s judging session.…

Step away from your feckin’ computer!

…and pick up your ProMarkers, Sharpies or any pen of choice.  Sketching is an essential part of the design process.  Fact. Technology plays a significant role in our daily activities but you need to pick up a pen and draw before diving in to the pixels. A great experience draws from a rich & diverse set of disciplines, and sketching is the best way to achieve great designs in a rapid, multi-discipline and collaborative way. Nothing frustrates me more than UX Practitioners that don’t sketch and UX Practitioners that say they can’t sketch.


As Ella Fitzgerald (and later Terry Hall) sang, It Ain’t What You Do (It’s the Way That You Do It). It’s the process of sketching wherein lies the power.  The proliferation of tools for UX folk has drawn some people away from the more effective hands-on approaches.  These new tools will enable you to craft your experience, but the journey that you take to get there is the difference between delivering a good and a great experience.

As for those who hide behind the excuse that they can’t sketch.  That’s baloney! Providing you can draw a few lines, boxes and even circles then you can visualize your idea as well as the next person. You don’t need to have advanced sketching skills.

Everyone can and must sketch.  If not, then you’re in the wrong profession. No other tools IMHO achieves all of the following:-

It’s inclusive. A sketch is democratic, in its creation and in its understanding. Anyone can do it. Sketching breaks down barriers by making everyone equal. A diagramming tool requires expertise.

It’s collaborative. Sketching is a good way of bringing people together and getting a faster feedback loop.

It’s disposable. If it doesn’t feel disposable then people will be reluctant to provide feedback and accept change.

Encourages feedback.  A straight line implies order and therefore, something considered or perhaps final where the wobbly hand drawn line is open, flexible, to be aesthetically ignored.  Because it looks rough, people are less afraid to criticize or offer suggestions. Low fidelity is more appropriate when higher level of feedback is required. Polished concepts cam put up barriers to feedback.

It’s Rapid. Sketching is a quick way to develop ideas and to explore different ones.  Even the fastest Omnigraffler can’t beat pen & paper!

It’s an effective communication tool. A doodle is worth a thousand words.

Shows the Design evolution.  It’s good to be able to look back at the original sketches that the final designs evolved from.

Engages the project team & client. A sketch frames an experience without getting caught in the detail.  It engages the client in the broader meaning of a solution and not the detail/minutiae. The project team and client needs to be engaged right from the offset as this helps forge a close respect and relationship which in turn produces better results.

Puts you in to a creative mindset.  Simply picking up your sharpie can put you in to the creative mindset.

It’s transparent. It’s all about nudity. Showing a sketch is naked idea presentation, which can show confidence in your process and concept; there’s nowhere to hide. The feeling of unfinishedness puts the focus more on the idea and the essence rather than inaccuracies or omissions.

Sketching is an essential tool in every UX Practitioners toolkit, and should be used at early concepting stages, when feedback and collaboration is most critical.  Formal deliverables can come later once the design options have been explored with pen & paper.

Note: Some of the above has been reproduced from one of my posts several years back.  I’m currently having a spring clean and closing down all my previous blogs, and therefore ‘borrowing’ a few bits here and there before they get lost forever.

Design Considerations for Building Mobile Apps

Today I participated in my first Apps for Good session with a class from Holly Hall Academy in Dudley. If you’re not familiar with Apps for Good then go read about this fantastic programme that encourages school children to use technology to tackle problems for social good.

Today was an opportunity for the young’uns (13 yo’s) to pitch some of their great ideas (via Skype) to Sophie Freiermuth and myself. We were impressed with their ideas, ranging from an app that provides advice on sexual health issues to one for finding out more on bullying and harassment. There were even ideas to find your perfect hairstyle and one that teaches you the Japanese craft of origami. We then shared insight and tips to help these young entrepreneurs to further develop their ideas.

I’ve summarised some of the key design considerations we discussed with the children below, with a few extra points (not covered) thrown in.

Think about the place of use
Mobile provides exciting opportunities because it allows users to interact in more places and in a more engaging way, and at different times of the day.   It’s important to understand the environment in which your customer may interact with the application. 

For example, consider what it means to your application if your target user will typically use your app in a public space to discuss confidential topics such as sexual heath or bullying. A voice-only mode may not be discreet enough, so considering the context will recognise the need for alternative ways to interact.

Provide functionality to help your target audience achieve their goal
Don’t make the mistake of discussing what functionality to offer before you have clearly defined what the goals are for the target audience. This avoids common failings such as feature bloat, where features are placed ahead of better experiences.  It is easy to create a rich feature list but the challenge is to understand the customer and pare down this feature list so that it does fewer things, better and in a simpler way, and all with the purpose of helping the users to achieve their goal. A good motto to keep in mind, “do a few things, and do them damn well.”

Storytelling is a powerful way to communicate design ideas. The narrative will validate the importance and effectiveness of your app in solving a real need.  One group told a compelling story of the build-up to a new haircut, of their fears and reassurances, which helped to ground their app in a real context and ultimately resulted in them only suggesting content and functionality that mattered.

Observe and learn from what engages you
Mario Kart is a masterpiece in game design. One tactic that Mario Kart uses to create stickiness is to reward you for winning a cup by unlocking new levels, characters or vehicles.  It helps to understand the small individual mechanics like this that make the game so much fun.

The children should learn from the things they find fun and engaging, and see how those design principles can then be applied to their ideas.

Are you giving your audience something of value? 
A successful app addresses real customers.  For every application that is the result of a rigorous user centric design approach there will be one that fails to consider who the users are, their behaviours, and how they will interact with the application. Keep asking yourself, who is your target audience and are you giving your target audience something of value.

The children should take every opportunity to talk to their target audience, be it other school children, teachers or parents. Research is a wonderful thing. They need to go get Guerilla.

Understand user behaviour
Apps tend to be more transient experience than traditional online experiences.  Customers use them briefly and move on.  These considerations are vital when designing apps. Long complex tasks are unlikely to be completed as users are distracted or disengaged. This is why mobile apps are seldom built to rely on long attention spans.

Observe, observe, observe.  Watch people’s behaviour and talk to them as they go about their business. Ethnographic research is important to help you understand how people interact with mobile apps.

Make the app easy to use
Even when these applications do address customers’ needs, many applications fail because of a poor design execution. Key characteristics that are fundamental to a mobile app include simplicity, ease-of-use and responsiveness.

The screen size provides obvious design implications. A usable application is one where the user can focus on the essentials.  It’s about stripping out the unnecessary to create a simplified user interface, which is easy to read.  The design objective is to keep the user experience focused on the task.  Screen clutter distracts and hinders the user from performing the intended action.  This is less about minimalist design but more about focused design.

Is your app finger friendly?
The mobile browsing experience is a different beast to the online browsing experience. With such a gestural interface, precision mouse control & clicks are replaced by the finger.  This enables users to interact in a far more natural and intuitive manner, responding to gestures such as tap, flick & pinch.  Successful implementation requires supporting standard gestures such as tap, flick and pinch appropriately and providing immediate feedback.  Gesture support manifests itself in the interface, as the layout is optimized for fingers, providing a finger tappable area for all tappable elements.  Fingers don¹t have the same level of precision as a mouse, so make sure all interactive elements are sized and spaced to optimise gestural interactions.

Provide an experience that is enjoyable and delightful to use
Users have high expectations for mobile apps and expect them to be enjoyable to use  - so whilst they are purposeful they need to delight. A delightful experience creates an emotional connection and a customer who is emotionally engaged will interact longer.

Make sure you app is intuitive
From the moment the launch screen appears it must be immediately apparent to the user what the application does and instantly understandable as to how to interact with it.  Users are impatient and if it takes too much time figuring out what to do then the user will tune out.

Know your phone
Most smartphones have a camera and GPS, and some have a voice assistant such as Siri.  Whilst you shouldn’t use features just because you can, do get to know your phone to make sure you fully understand what it can offer you.

The group with the idea for a sexual health app, made great use of an intelligent personal assistant to provide an easy and intuitive way to ask questions.

A phone has its limitations
Users have high expectations of performance.  Therefore design your application with bandwidth in mind. Desktop Internet experiences provide a visually engaging experience without the same bandwidth constraints, therefore images and rich media are heavily used. However, when it comes to mobile design, these rich elements can do more harm than good if they provide a sub-optimal experience.

Hopefully the school children found the session useful.  I found it fun and inspiring, and I look forward to the next session.  Thanks to Andy Steadman (from Holly Hall Academy) and Myrian Schwitzner (from Apps for Good) for organising.

Making UX Happen

Last night’s UKPA UK workshop on Making UX Happen reinforced my view that the User Experience community are guilty of many of the failings that we label as “the client doesn’t understand us.” Yesterday at times felt like the UX equivalent of alcoholics anonymous, as UX practitioners slowly stepped forwarded with confessions that there is more they could be doing to make UX happen.  My response to “the client doesn’t understand us,” has always been “well, you clearly didn’t do enough to help them  understand.” We regularly hide behind our rich toolkit of methods, great consumer insight and design thinking that all has its focus set firmly on the end-user. We drop our guard when it comes to understanding the client. The client has needs, behaviours and attitudes – and we need to focus in on these if we want our discipline to be better understood and to be ‘agents of change’ in driving business transformation. We have consumer empathy in abundance, but we lack empathy for our stakeholders and the business. We need to grow up and recognise that our primary aim is to fulfill the business objectives set out by our clients. Too often we are focused purely on producing the project outputs that were specified in the project plan, ignoring the other elements that are fundamental to the projects success. But these outputs don’t matter if they aren’t adopted by the stakeholders. We are responsible, along with the wider project team, for their adoption.

Do we understand all the stakeholders that can impact and influence a decision? Do we know who to engage, when to engage them, and how? Are their expectations of our customer-led approach and of the final experience correctly aligned? If we don’t know who to engage, or don’t have a strategy for engaging and communicating with our stakeholders, then this severely reduces our effectives, and increases the likelihood that our vision of the experience will not happen. Stakeholder analysis and management, communications strategies and plans, and expectations management may all sound like dull business talk, but these are techniques that we need in our toolkit now. Terms such as Power-Interest analysis and RACI matrix should be as much part of our vocabulary as personas and wireframes!

Thanks to UXUPA UK for hosting this event, and thanks to Jason Mesut, Timothy Loo and Marcus Smet for running a very worthwhile session.

I’ll follow up with a more in-depth post on more of my takeaways from last night’s event.

What does it take to design experiences

As I scrawled the estimates for a routine design phase on a whiteboard, a colleague was intrigued by the way I broke down my estimates. It’s a frustrating aspect of agency life that many people think of designing experiences in terms of wireframing. I adopted a simple technique to help break through this production mentality and buy the team ‘time to think’ – a rare commodity at the best of times!

It’s simple…I estimate each component, screen or section against three attributes; Talk, Explore & Communicate. This additional granularity enables me to provide more accurate estimates. It also helps the wider team to better understand what the design process actually entails. I loosely define these attributes as follows:-

This is how much time I need to gather all the necessary information before I have the majority of information required to explore the design options. Depending on the complexity of what I’m designing, a water cooler moment might be enough, or I may need one or more workshops to make sense of the requirements.

Design is not a straight path and not every design challenge has a single solution. I need time to explore the different design options. This is the heart of the design process, where I think through the design problem, applying lo-fi methods to explore and refine ideas in a fast and iterative manner until one is reached and agreed on. Computers are not invited.

And finally, this is where I communicate the information architecture and interaction models in sufficient fidelity to be implemented. It’s important to pick the right comms tool for the job, be it final designs annotated with post-it notes, omnigraffle wireframes or interactive Axure prototypes.

This isn’t rocket science, but I find this simple technique results in more accurate estimates. A single number against a screen often gets squeezed as the wider team fail to understand some of the complexities and the design thinking involved to craft something that meets the business goals and make the customers happy. I got in to this game to craft customer experiences that make a difference and this technique is a small step in shifting the focus to where it needs to be.

Just Say NO to Wireframing

I’m not against the process of Wirefaming. Wireframes are a valuable communication tool in every Experience Designer’s toolkit. It’s the term itself, Wireframing, that we need to push back on! This word is commonly misused and the cause of considerable frustration for those of us that design experiences. Yup, we Design Experiences. The problem is that in many organizations Wireframing has become synonymous with Design.

The misuse of this word highlights a fundamental lack of understanding of what us so-called User Experience Designers do and distorts the perception of how we do what we do to people less familiar with our craft. Worst of all, it instills a production mentality, of a conveyer belt that churns out wireframe after wireframe after wireframe…

If you are asked to wireframe something, correct them and ask whether they want it Designed instead.  This is not semantics, but a critical re-education of what Experience Design entails. By calling it what it is, Design, we invite a conversation beyond a diagramming and communication tool, a conversation which focuses upstream where the ideas and thinking live.

Design is not a straight path. Exploration allows us to think through the design problem to get the right design out of the many possibilities.  And you cannot design an experience in a vacuum – it relies on cross-discipline collaboration. This doesn’t happen in a diagramming tool. This is why we use Design Techniques such as lo-fi sketching to explore design options, invite commentary and gain design consensus. This is the heart of the design process, and it’s where the magic happens.

Once we’ve explored the design options, the final step in the design process is to communicate the experience; the interactions, behaviours, layout and much more. Many factors influence our choice of communication tool, and it’s important to agree the most efficient way to communicate the designs so that more time can be spent truly designing the experience. Wireframes are one of many tools available to communicate the experience. Wireframing Is NOT Design but it may be part of your design process

It’s still early days for our industry and it’s important we take every opportunity to help people understand what we do.  If we fail to explain our craft today, then tomorrow could be a dark n’ miserable world for User Experience practitioners.

[Image of the Grange Hill 'Just Say No' Campaign borrowed from Pink Label Marketing]

To freelance or not to freelance, that is the question

As 2012 draws to a close, I must admit that I am somewhat befuddled. Everything seemed so straightforward in August. I want to work on strategic head-hurting customer-led challenges that facilitate true business transformation. The way I saw it back then, is that having the freedom and control to select what I work on would be the way to achieve this. So I decided that after over 15 years of permanent employment, 2013 would be the year I go freelance. Sounds simple, eh!

There is no shortage of agencies with ambitions to transform businesses, but in reality most are simply designing what their clients ask for. Freelancing therefore felt like the obvious career choice, putting me in control to work on those projects, both strategic and tactical, that drive real business value.

And then the confusion began.  As I shared coffee, beer and lemsip, with friends, and friends of friends, in senior roles across the industry, they reliably informed me that this work exists in regular supply for permanent employees. The challenge is in knowing which agencies have built strategic relationships with their clients and are having grown-up customer-led conversations. As these encouraging and tantalizing conversations continued, I started to question, to freelance or not to freelance? 

I have simple needs, to deliver great experiences that make a real difference. To freelance or not to freelance may be a red herring. Both offer the kind of work that really fires me up. The clear advantage of going freelance appears to be having more control over what I work on, and therefore increased likelihood that I’ll work on those things I love doing.  Maybe I am suffering the career equivalent of a midlife crisis, as I consider trading in a secure and enjoyable career for a sexier but riskier model.

To be continued…

Dear Santa, all I want for Christmas is

… a bona fide music discovery service.

I hold online music services accountable for a generation raised on full-fat musical dross. These online services boldly proclaim ‘we will help you discover great new music’ but when we give them license to recommend, they provide more of an apologetic sideways shuffle than an Indiana Jones style adventure of musical-discovery.

The digital era has changed the musical landscape. Aspiring and established artists can produce and self-publish their music with relative ease. More music is being produced than ever before. I whole-heartedly embrace this shift in the musical landscape but at the same time this demands these so-called music discovery resources to up their game and rethink the role they can play.

I Imagine a conversation with John Peel…

I start by telling him about my favourite tracks of now and yesteryear. John listens then puts a finger to his lips, whispers shhhhhhhh, and slips me a music recommendation.  It’s not the same genre, a labelmate, similar tempo, an album with a Pitchfork rating of 8.6 or above, or something my friends like, but a potent mix of his indisputable music knowledge and his intuition of what would tickle me.

So Dear Santa, please bottle up John Peel to create a truly sophisticated and meaningful recommendation algorithm that exposes the good people to some of the truly amazing music being made.

Are you serious about your personas?

There are hundreds, if not thousands of articles on the persona creation process, debating the merits (or lack) of personas, contrasting the different research methods applied, through to beauty parades of how a persona is documented.

Often what gets overlooked is the art of adoption. How do you ensure that any in-depth research you invested in creating the personas gets integrated in to your design work and you don’t simply end up with a document that sits gathering dust? My cynical self has witnessed persona creation as a checkbox in a so-called customer-led design process, with no real appetite to ensure they play a pivotal role in the design of something useful.

We need to talk more about how we ensure that our personas are adopted. I don’t just mean noise in the twittersphere or rambling posts such as this, but as a step in each project’s experience design process. Ouch!

Defining your Persona adoption plan & tactics should be a key step right from the outset of your persona creation process. Do not be afraid to include it in your plan – it’s essential. This won’t take long or bust the budget, but it’s important to put this topic high up on the project’s agenda to drive the value that personas will deliver if embraced and adopted by all the stakeholders.

There are three parts to this:
• Format and style of the deliverables
• Key success criteria for the chosen format
• Rollout plan for communicating the personas to your stakeholders

First up you need to agree on the format for communicating the persona. Anyone that stands by his or her persona document template regardless is doomed to fail. We need to understand the needs and behaviours of the stakeholders too, to document the persona in a way that is compelling, memorable, and most importantly – one that they will use.

With a format chosen, be it poster, document or video – you need to identify what criteria to evaluate this deliverable by. All that Infographic trickery that is creeping in to personas doesn’t necessarily create an engaging and compelling story. How you ensure you achieve a realistic quality by using say, a first voice narrative, is essential. You also need to have these conversations upfront to ensure you organize the appropriate resources. For example, which storyteller supremo will be adding a sprinkling of fairy dust to make your persona narrative more compelling? I’ll pen a separate post on this to discuss some interesting work I’ve been doing to improve Persona Recollection.

When the documents have been carefully crafted to represent the personas, typically they get emailed around the team and/ or dumped on the project portal. Maybe they also get stuck on the walls. That’s not good enough. You need to work hard to ensure they are effectively communicated to all stakeholders. I recently heard of one company hosting a Mr. & Mrs. type quiz over a boozy after-hours meal to communicate their personas. The next day as the team shrugged off their hangovers they could recollect the personas in intimate detail! Be creative in what you do to ensure the entire team really take them to heart, not just you! This doesn’t happen by chance, you need to plan for this.

It’s simple. Before you jump straight in to the persona creation process, stop and plan what needs to be done to ensure they are effectively communicated and adopted by the team.

Design With Safety In Mind

The street is full of pedestrians hunched over their phones, bumping awkwardly into other morning commuters. As they stumble through crowded streets these mobile users are blissfully unaware of the impending dangers.

Using a hand-held mobile device while walking is having a significant influence on pedestrian safety. 

As our lives get busier and apps get richer and more engaging, distraction injuries will rise.  We are bombarded by information and surrounded by playgrounds of choice. Becoming distracted has never been easier.  Our savior to the perils of distracted walking lies with a new breed of applications and devices built with our well-being in mind, to makeus more aware of our surroundings by alerting us of unsafe situations such as oncoming traffic.

Welcome to Safety-Conscious App Design.

There is a new generation of apps that have launched with the right intentions – to help you keep one eye on your surroundings, whilst you use your mobile device.  Type n’ Walk is one of many, which uses the rear camera to give you a forward view of the world so that you can text safely. Combined with your peripheral vision you will have enough visual information to walk the streets safely. Well, that’s their claim.

Whether apps like Type n’ Walk are a genuine aid to our well-being or are more likely to alert us to hazardous dog doo than an approaching vehicle will be debated. But what is important is that apps are starting to care about our safety.

Safety-Conscious App Design occurs both intentionally and by chance. Take Snackr for example. Snackr reads out personalized news headlines in bitesized chunks. Users can listen to Snackr to get their news fix and still scan the environment.  There is a growing trend towards apps that read out content, such as Tweetspeaker. But Audio alone is not without its dangers. Many recorded pedestrian-vehicle collisions occurred when headphones were being worn.

As the ‘always-connected’ generation becomes the ‘obsessively-connected’ generation it’s unlikely that we’ll put the mobile down quite yet.  New applications need to consider this. Safety features in the occasional app may just become default functionality in all apps. Apps will be developed with an in-built ‘walking’ mode.  Technology will also become more sophisticated, and in the future our devices will be able to detect vehicles or people approaching (or even fountains!). Mobile devices with embedded sensors will allow applications to understand the environment around them and therefore be used to avoid accidents.

And all of this really does matter.  What’s important is that we consider how people use their mobile devices. We need to design for people, for real-world behaviors, and for real-life scenarios.  We need to understand the environment and craft experiences for context. And if users’ interactions are putting them into potentially dangerous situations then we have an opportunity to help.  We can deliver the tools and features for users to achieve their goals safely.

[originally posted on my Typepad blog but mysteriously all my posts disappeared, so re-posting in this new space]

1 2  Scroll to top