We've launched! And we have bugs! And we have to get on a plane so it'll be a day or two! Full details and Frequently Asked Questions inside.
- We've been featured on a lot of blogs today (thanks Lifehacker!) and we just crested our first thousand users, so welcome!
- Metric!: We will shortly (hopefully by the end of the day) allow you to set km as distances instead of miles and liters instead of gallons (and we'll add imperial gallons and L/100km type calculations as well).
- Motorcycles/scooters!: By early next week we should have a way to enter in your year, make, and model of two-wheeled vehicle, and we'll use submitted data to build up a database of all known bikes being ridden out there.
- My car/model/engine isn't listed: By next week we should have ways to enter in data that is outside the bounds of what we list (we started with a somewhat complete list of cars available in the US).
- Locations of fuel-ups? Highway vs. City estimates? Prices in something other than US dollars? Email/SMS input? Upload API?: Yep, we've gotten a ton of great ideas that we'd like to also add in the next week or two and these will be some of them. We have a complete running list of major features we're still working on in a previous post.
If you have any other questions or suggestions for data you'd like to see (especially in non-US countries -- how does your country typically report fuel economy?) drop them in here.
Wish we could post more than ONE post per WEEK to what is supposed to be a FORUM. What's up with that. It's a forum. There won't be much discourse if you restrict to one entry per week. Just a friendly suggestion. Happy launch day!
PS - The iPhone interface is a little messed up as well. The input fields are HAH-YUGE and go off the screen to the left when in portrait mode. In landscape mode the fields fit but the header is shrunken. FYI from one webdeveloper to another.
I noticed a user with the same type of car as mine with wildly varying statistics (e.g. impossible >1000 miles / tank fill ups, etc.). Will there be a way to flag users who enter impossible data to keep the numbers more accurate? The statistics here could start influencing purchase decisions eventually and bad data would be a terrible thing in that case.
Not sure if this has been posted before or not, but can you include support for TWITTER? I'm used to twittering status updates and a simple twitter input interface say: @fuelly 104.1 3.759 7.465 would represent how many miles I travelled, the price I paid for the gas, and how many gallons were purchased (MPG).