Rewrite an existing Palm webOS application named "PitStop" for Android.
Use standard Android SDK, API level 7 (Android 2.1 Eclair).
Storyline as follows:
* User sits in his car after he put fuel in it and opens app.
* No internet connection is needed for normal operations!
* First screen shows form for entering values and a statistics table showing the last x entries of the currently selected car.
* User enters amount of fuel.
* User enters distance traveled. This can be done either relative using the trip meter or absolute, using the odometer.
* If a relative distance to the last refueling can be determined, the average consumption is displayed immediately.
* User enters money spent on fuel.
* User chooses car. (3 cars fixed)
* User hits "add" button, statistics for selected car is updated together with current timestamp.
* Statistics shows a total row, summing up fuel and distance and showing a total average consumption.
There are 3 additional screens:
Configuration screen:
* Distance mode: relative via trip meter or absolute via odometer
* Length of statistics table shown: between 3 and 30 entries
* Rename cars (default is "Car 1", "Car 2", "Car 3")
* Units:
* Fuel unit: l (liter), gal (gallon), kg (kilogram)
* Distance unit: km (kilometer) or mi (miles)
* Consumption type: distance-per-fuel-unit (like miles-per-galon, mpg) or fuel-per-100-distance-units (like liter-per-100-kilometer, l/100km).
* Currency sign: ?, $, ?
Statistics screen:
* Shows all records for car selected on front screen.
* Each record can be selected and edited or deleted.
Record edit screen:
* Every detail can be changed, even timestamp.
...see details for more...
## Deliverables
Rewrite an existing Palm webOS application named "PitStop" for Android.
Use standard Android SDK, API level 7 (Android 2.1 Eclair).
Storyline as follows:
* User sits in his car after he put fuel in it and opens app.
* No internet connection is needed for normal operations!
* First screen shows form for entering values and a statistics table showing the last x entries of the currently selected car.
* User enters amount of fuel.
* User enters distance traveled. This can be done either relative using the trip meter or absolute, using the odometer.
* If a relative distance to the last refueling can be determined, the average consumption is displayed immediately.
* User enters money spent on fuel.
* User chooses car. (3 cars fixed)
* User hits "add" button, statistics for selected car is updated together with current timestamp.
* Statistics shows a total row, summing up fuel and distance and showing a total average consumption.
There are 3 additional screens:
Configuration screen:
* Distance mode: relative via trip meter or absolute via odometer
* Length of statistics table shown: between 3 and 30 entries
* Rename cars (default is "Car 1", "Car 2", "Car 3")
* Units:
* Fuel unit: l (liter), gal (gallon), kg (kilogram)
* Distance unit: km (kilometer) or mi (miles)
* Consumption type: distance-per-fuel-unit (like miles-per-galon, mpg) or fuel-per-100-distance-units (like liter-per-100-kilometer, l/100km).
* Currency sign: ?, $, ?
Statistics screen:
* Shows all records for car selected on front screen.
* Each record can be selected and edited or deleted.
Record edit screen:
* Every detail can be changed, even timestamp.
Additional requirements:
* Data recording must be persistent. (Use Android's SQLite feature!)
* No conversion of values, when user changes units.
* A change of distance mode must not harm recorded data.
* Configuration must be persistent and reapplied on startup. (Use Androids "Shared Preferences" feature!)
* All text has to be localizable, even stuff like default car names.
* English is default and required, localize in your language if you like.
* Timestamp is to be localized.
* Numbers are to be localized.
* Data has to be exportable via E-Mail containing data in CSV (Comma-Separated-Values) format.
Additional information and screenshots can be found here:
<[login to view URL]>
<[login to view URL]>
<[login to view URL]>