|
I hear what you're saying, hopmedic. A native app means adding a fuel-up could be a little faster. We can't speed up Opera, but we can play with the design if that's a problem--and that's much easier than designing, documenting, and maintaining an API.
I realize these things are all in the realm of possibility, but we have constraints of time and attention. In a world with unlimited time and budget there are stacks of things we'd love to do with Fuelly. An API is on the list, but that will take a good chunk of time to design, build, and test. Then with every addition comes more responsibility. Suddenly we'd be spending time supporting developers building apps, answering questions, troubleshooting. So the gains need to be fairly significant to push building an API to the top our wish list.
I hear what you're saying about the inefficiency of loading and scrolling, and honestly since we added SMS fuel-ups I use that most of the time. But I'm not sure the tweaks that a native app would make possible are worth the effort.
|
Funk 
Threaded Mode
