Changes

Jump to: navigation, search

MDN/Development/CompatibilityTables/Data Requirements

431 bytes added, 14:40, 20 February 2014
Targeted audience
=== Targeted audience ===
In order to better understand want we want to do with compatibility data, wa we identified a few profiles that need to be kept in mind as they well as their possible motives. Those profile profiles will be refine help while moving to a more formal UX step in the project.
==== web developers ====
Web developers always have a hard time while working in a cross browser environment. To avoid that, they need to be able to found detailed information regarding the feature features they are working on and it's their availability among browser browsers as well as information to bypass a possible lack of implementation. As they are mostly seeking such information during their work time, they have very few time to dig down and need quickly accessible straight forward information.
==== App developers ====
App developers are a bit different from quite similar to web developers as , but they wish to focus on a smaller number of platform (if not just one). To that end, they needs detailed information about implementation of feature on a specific browser or version of a browser. As they are mostly manipulating cutting edge technologies, they need a very high level of information about each features and their availability, seeking for each small piece of information to improve their work.
==== web architects/lead dev ====
Those are people building the technical strategy beneath a project. They need fully detailed information about browser compatibility in order to take rational and accurate technical decision that can ease or jeopardize their project in the long run. As they plan things, they have time to dig deep if necessary.
==== project leaders ====
Confirm
630
edits

Navigation menu