Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to use trip miles instead of odometer. #23

Open
wdkapps opened this issue Apr 8, 2014 · 4 comments
Open

Option to use trip miles instead of odometer. #23

wdkapps opened this issue Apr 8, 2014 · 4 comments
Assignees

Comments

@wdkapps
Copy link
Owner

wdkapps commented Apr 8, 2014

User review: Overall, a good app, but would be better with the option to use trip miles instead of odometer.

@wdkapps wdkapps added this to the V2.0 milestone Apr 8, 2014
@wdkapps wdkapps self-assigned this Apr 8, 2014
@wdkapps
Copy link
Owner Author

wdkapps commented Apr 8, 2014

I have no idea how this would work. Would the app just add the trip miles to a previous odometer value? If you don't track all gas purchases and mileage the statistics will never be accurate. I'm up for ideas.

@wdkapps wdkapps removed this from the V2.0 milestone Apr 20, 2014
@cyrildtm
Copy link

Sometimes one may know the exact trip miles of one trip. But he/she has forgotten to read the odometer immediately after the trip. For example a case in which a user keeps the trip miles and fuel amount on a notebook. A few days later he/she becomes free, and would like to enter the data into the app. But at that time the odometer reading has been incremented, because he/she has driven it to work after that trip.

It might be better if we have both options to record the miles. In addition, one could calibrate the app by entering the true odometer reading, maybe after several weeks only entering trip miles, without entering fuel data.

I'm your user who likes your app a lot. Hope this could help.

@wdkapps
Copy link
Owner Author

wdkapps commented Aug 30, 2014

Thanks for the feedback. It does help to understand what a user is looking for. But I'm not sure how to tie that in with the existing app features.

If we add a new feature "Add Trip" for example, and it allows a user to enter:

  • trip date
  • trip distance,
  • trip fuel used
  • trip fuel cost

What should FillUp do with that data? The current Log is based on odometer values. So do we add that trip to the Log based on some ending odometer value and assume it indicates that some data was lost since the previous odometer entry? Or do we track trips in a different "Trip Log"?

@cyrildtm
Copy link

A simple way is convert trip miles to odometer data by simply adding. Then treat the user input as if it were a typical odometer / fuel data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants