Mobile App/Roadmap: Difference between revisions
(Created page with "The applications are currently written in HTML. It may be possible to reuse the template mobile applications Wikipedia to go faster in development. There are advantages to hav...") |
No edit summary |
||
| Line 1: | Line 1: | ||
The applications are currently written in HTML | The applications are currently written in HTML. | ||
There are advantages to having native applications : | There are advantages to having native applications : | ||
* It allows users to do more tasks | * It allows users to do more tasks | ||
| Line 15: | Line 15: | ||
* Add more fields that are mobile optimized (directly a numeric Keypad for weight, for example) | * Add more fields that are mobile optimized (directly a numeric Keypad for weight, for example) | ||
[[fr:Applications mobiles]] | [[fr:Applications mobiles]] | ||
[[Category:Mobile]] | |||
Revision as of 15:58, 2 May 2015
The applications are currently written in HTML. There are advantages to having native applications :
- It allows users to do more tasks
- Applications are more responsive and have a more robust appearance
- Ability to automatically add the place where the product was scanned
- Smart autorotation for barcode in android (no need to turn the phone)
- Can add pictures taken with the phone photoroll
- Send notifications from time to time to propose to log a product.
- Create an account on openfoodfacts from your mobile
- There are areas where the touch make much sense ( eg. rotate images, select the images and image areas to identify logos, packer codes, nutritional information... )
- Ability to edit section by section
- Mobile autocompletion
- Propose a game that asks simple question after simple question to tag existing products
- Add a timer for cooking based on the barcode and our data
- Add more fields that are mobile optimized (directly a numeric Keypad for weight, for example)