canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093
edits
DeveloperExperience/Personas: Difference between revisions
DeveloperExperience/Personas (view source)
Revision as of 14:54, 27 November 2012
, 27 November 2012no edit summary
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[http://www.pragmaticmarketing.com/resources/The-Power-of-the-Persona User personas] (not to be confused with [http://mozilla.org/persona Mozilla Persona]) are intended to describe realistic people that represent a market segment that is worth discussing. Using personas helps make discussions concrete and ensure that everything we do is built around real [http://www.forbes.com/sites/stephenwunker/2012/02/07/six-steps-to-put-christensens-jobs-to-be-done-theory-into-practice/ "jobs to be done"] for which people will choose Mozilla's offerings. | [http://www.pragmaticmarketing.com/resources/The-Power-of-the-Persona User personas] (not to be confused with [http://mozilla.org/persona Mozilla Persona]) are intended to describe realistic people that represent a market segment that is worth discussing. Using personas helps make discussions concrete and ensure that everything we do is built around real [http://www.forbes.com/sites/stephenwunker/2012/02/07/six-steps-to-put-christensens-jobs-to-be-done-theory-into-practice/ "jobs to be done"] for which people will choose Mozilla's offerings. | ||
Ideally, these personas will reflect people who have differing needs and workflows. | |||
These personas will generally be used as starting points with variations appearing in product requirements as needed to properly highlight the requirements. | These personas will generally be used as starting points with variations appearing in product requirements as needed to properly highlight the requirements. | ||
| Line 24: | Line 26: | ||
He has no experience building mobile apps, a bit of experience making web sites but not much in terms of mobile web. He has programming experience from his coursework and random projects he has done in C++ and Java (Minecraft mods, for example). | He has no experience building mobile apps, a bit of experience making web sites but not much in terms of mobile web. He has programming experience from his coursework and random projects he has done in C++ and Java (Minecraft mods, for example). | ||
= Jimmy (learning frontend technology) = | |||
As a five-time PyCon speaker, Jimmy is an experienced developer. He's been doing web development for years, but it's been the kind of web development where the server drives the experience entirely. Now, he's getting into the newfangled HTML5 stuff. He's learning about doing more with JavaScript than just validating form inputs. He's learning about build steps, new tags, CoffeeScript and LESS, new APIs. It's a bit overwhelming, honestly. | |||
Jimmy has been relying heavily on MDN and Stack Overflow as he has been coming up to speed on new projects that require him to build more sophisticated front ends. So far, he's having a good time of it. | |||
= Emily (corporate web app developer) = | = Emily (corporate web app developer) = | ||
| Line 35: | Line 43: | ||
John lives and works in Schaumburg, a suburb of Chicago. He works for a 20 person web development company. A typical project for them involves 3-5 people working on the project and lasts 6-12 months, though they're sometimes called upon to squeeze in a quick (1 month) project and they also have some long term customers for which they are maintaining apps that they've been in the past. | John lives and works in Schaumburg, a suburb of Chicago. He works for a 20 person web development company. A typical project for them involves 3-5 people working on the project and lasts 6-12 months, though they're sometimes called upon to squeeze in a quick (1 month) project and they also have some long term customers for which they are maintaining apps that they've been in the past. | ||
John, like the other developers in his shop, describes himself as a jack-of-all-trades. While working on a project, he'll bounce around from doing a bit of Python on the server, to building out a UI in JavaScript, to keeping track of some stats with Redis. | Some of the company's projects have demanded more people than were available and the company has outsourced some of the development. John has had to integrate the outside developers into his day-to-day workflow. | ||
John, like the other developers in his shop, describes himself as a jack-of-all-trades. While working on a project, he'll bounce around from doing a bit of Python on the server, to building out a UI in JavaScript, to keeping track of some stats with Redis. Many of their projects have PHP servers, but they've been gradually shifting to Python. | |||
On past projects, John (and others at his company) have been burned by adopting some promising new technology a bit too early. Since then, John has tended to wait until a new library or tool has proven itself. | On past projects, John (and others at his company) have been burned by adopting some promising new technology a bit too early. Since then, John has tended to wait until a new library or tool has proven itself. | ||
| Line 64: | Line 74: | ||
Management at SuperTodoer is trying to grow usage of their application outside of the US and they see Firefox OS as an opportunity to break into the Brazilian market. The company is willing to buy Claire a device to work with. | Management at SuperTodoer is trying to grow usage of their application outside of the US and they see Firefox OS as an opportunity to break into the Brazilian market. The company is willing to buy Claire a device to work with. | ||
= Pamela (super-scale web app developer) = | |||
Pamela is an unsung hero who, over the past 5 years, has helped several areas in SuperHighTrafficSite.com grow to be among the busiest web properties. Her company is relentlessly devoted to performance, wanting to keep application responsiveness down to 60ms for any interaction and letting new content scroll into view super quickly. | |||
To the untrained observer, SuperHighTrafficSite seems fairly straightforward, but the reality is that they're constantly pushing the bounds of what webapps can do, taking advantage of new capabilities like WebRTC as soon as possible for access to camera and microphone, or using Web Sockets for real time information display or Web Workers to speed things up. | |||
Pamela is a front end engineer. SuperHighTrafficSite has separate teams for the front end and back end, because they're both complicated. | |||
As an early employee, Pamela made enough money on the company's stock that she really doesn't need to work any more. She loves it too much, though, and can't help herself. | |||
= Rick (ad agency designer/developer) = | |||
Rick works for Cranblotz and Fitch, a "digital agency" that creates ad campaigns and other creative work for businesses of many sizes. Cranblotz and Fitch campaigns are often built on tight schedules and require a tight combination of programming and design. | |||
Rick considers himself a designer first and foremost, but he has taught himself to use HTML, SVG, CSS and JavaScript effectively to create compelling animations and learned many tricks to get his animations to show up as smoothly as possible on as many devices as possible. He makes use of libraries where he can and has even contributed some code back, but he often resorts to coding to the "bare web" when the animation is just not smooth enough. | |||
Secretly, Rick doesn't mind it when people call him a hipster. | |||
= João (indie game/freelance web developer in Brazil) = | = João (indie game/freelance web developer in Brazil) = | ||
| Line 74: | Line 102: | ||
Given that this is a side project for fun, João wants to keep his costs low. | Given that this is a side project for fun, João wants to keep his costs low. | ||
= Duke (big game developer) = | |||
Duke works at a large scale game developer known for a variety of games (some massively multiplayer, others that push the boundaries of graphics power, still others that push the boundaries of good taste). Duke has been with the company for a decade and has proven himself to be a coder that gets the job done. | |||
Normally, Duke does not get involved in porting projects, but he's making an exception because this new project offers some new challenges: he's helping to port one of their big projects to the web. Duke is leading the way in evaluating the options they have, including a complete rewrite of the engine in JavaScript. | |||
Duke's favorite food is spaghetti. He claims that eating the spaghetti helps ensure that his code is well-organized. | |||
= Sharon (mobile app developer) = | = Sharon (mobile app developer) = | ||
| Line 106: | Line 142: | ||
Amanda lives in Toronto. | Amanda lives in Toronto. | ||
= Reggie (code installed at customer site) = | |||
Reggie's company builds an enterprise product that is installed behind company firewalls (ServerThingBox). ServerThingBox has a browser-based user interface, the development of which is very similar to the development of any web app (you could imagine Reggie being like other personas above). Companies that use ServerThingBox upgrade infrequently and have different support needs from the "software as a service" model that is popular today. | |||