Difference between revisions of "App development process"
Josef.Noll (Talk | contribs) (Created page with "= Experiences from App Development = This page provides suggestions for App Development for People not being IT specialists. Though you'll find a range of tools for creating a...") |
(No difference)
|
Revision as of 08:56, 6 July 2017
Wiki for ITS | ||||||
---|---|---|---|---|---|---|
|
Experiences from App Development
This page provides suggestions for App Development for People not being IT specialists. Though you'll find a range of tools for creating apps, using technical tools might take your focus away from simplicity.
KISS - Keep It Simple and Stupid, should be the basis for every app. Studies have shown that with every click you loose about 20% of your customers. Thus, with three clicks you only have half of your app-users again (from 100% > 80% > 64% > 51%).
Thus, our recommendation is to have the following procedure in mind when you develop your apps
1. Brainstorming for main purpose
Have a brainstorming with your colleagues to identify what are the key topics you would like to achieve with the app. Which functionality are you out after,
see: App_development_process, in short:
- 1) use Post-ITs for each page...1 -> 1.1 -> 1.1.1 ->...
- 2) describe all links (in IT terms: wireframe)
- 3) translate each Post-IT into one xxx (Pencil, Balsamiq,...) ("mock-up which you can show to people for comment"), include links
- 4) develop the app
IT-specialist recommendation
Jan (Cystinet project) recommends to use Axure RP 8 (http://axure.com), where a University can ask for a free Teacher license. See DigI:AI-004
--Josef.Noll (talk) 10:56, 6 July 2017 (CEST)