An Android App based on LVF

[Nathan]

Hello, all. I wasn't too sure where to put this thread so I decided to put it in the Off-Route section of the forum.

Lately I've been thinking about developing an Android that delivers similar (NOT the same) functionality as the London Vehicle Finder. The idea of the app is to help the user check the time for a bus at a particular stop as well as delivering details of the physical bus that is due at that bus stop (such as the number plate, etc). I figured it would be easier to have a native app to use as opposed to having to visit the browser.

Developing an application like this would take me a very long time, as I need to get to grips with the API and the appropriate IDE (the thing I use to code the program). If I do go ahead with the project, I will probably need a group of Beta testers from this forum (or any other places) so I can iteratively add features to the app to make it better for the user. The app may sound basic right now, but with the help of the beta testers I'm sure I'll be able to make it more complex.

LVF Owner, I would greatly value your input on this potential project of mine. If I were to make this, how should I set up the databases? (What entities should I include?)

Knowing my luck, I bet someone has already gone out and made something like this  .

[snoggle]

The Live London Bus Tracker android app will display the registration of the bus when you select an individual arrival for a given stop. Not quite what LVF gives but closeish. I am sure there are other apps that also display this info too but I have not checked every London Bus app. There is also the "Live London Bus Map" by Matthew Somerville that shows reg numbers when you click on a moving bus on any given route.

play.google.com/store/apps/details?id=com.appeffectsuk.bustracker&hl=en_GB

I have to confess I don't see the point in having an app when there is a working website. You need the same comms connection from a mobile phone to make either an app or a website work and LVF is not exactly a complex or difficult web interface to deal with. Far too many apps fail to keep up with updates to the api - the main one I use still has the W11 running via the Bell Corner, the 76 terminating at T'ham Garage and doesn't recognise any of the new stops at T Hale! I'd rather app developers kept up with the underlying data than faffed around with the interface or "back room" stuff. Again the bus app I use most was recently "updated" in such a way that it was rendered unusable - how about white text on a white background? Very readable - NOT!

I guess my subtext here is that if you do develop an app then make sure you can commit the time to keep it up to date and relevant. If I understand matters properly then there is a load of support effort behind LVF to keep it running and especially to manage the underlying database of live and withdrawn vehicles and to try to keep vehicle histories as accurate as possible given Countdown data is not necessarily accurate in and of itself (e.g. buses in service but not communicating due to faulty I Bus kit). If you were to try to link reg numbers to vehicle fleetnumbers you'd face the same massive data management task that Brian C faces. Also don't forget that TfL routinely muck up the vehicle IDs / reg numbers just to add some extra variety to life to keep everyone on their toes!