• Read Me
Answers to common questions
Thanks for taking the time to read the online help. There is a lot in London Bus and a few minutes spent here will help you get the most out of the application.
Why is journey planning so slow!
This is down to the response time at the Transport for London journey planning server. London Bus retrieves all plans in one hit, this way once you have a set of journey plans as you select & view each one the application does not need to go back to the server again. This makes navigating & deciding on the best plan for you much faster. It can take upto 2 minutes to receive some plans; journey planning is generally faster over a WiFi connection but it does work over Edge & 3G. The TfL server will sometimes slow up at the beginning and end of each work day.
Why is there a splash (start-up) screen?
The application will display a screen at start-up while it is loading, the screen is displayed for the duration of the load only and is not an ad. Behind the scenes a lot happens at startup time, what you are seeing here is the trade off between taking an extra second or two to load essential data upfront versus making the user wait as various sections are navigated. For London Bus, taking the hit upfront is far better, once its loaded the experience is smooth and seamless.
I am open to other suggestions for screens, however if I were to take the screen away it would display a black screen for exactly the same amount of time. The splash screen does not slow the loading of the application.
Why isn’t anything updating?
By default your device will join any Wi-Fi service it can, sometimes these services have no initial password to join but do have a secondary login (for example many Airport lounges) in which you pay for wireless access. You can confirm this is the case by loading Safari; it will usually take you to a site to join as a member. Your device will favour using a wireless connection. This means you can end up the situation where you can see that you have a network connection, but can not receive any status updates, departure information or even correctly locate.
To work around this, enter the device’s ‘Settings’ select the network under ‘Wi-Fi’ and ‘Forget this Network’. Or simply turn off Wi-Fi to use the 3G/Edge network. Don’t forget to turn it back on when you’re at familiar wireless spots.
I have a bug & the app crashes, should I just trash it in a review?
Please let me know if you have any problems using the application, I fully support London Bus, and it has very active development. I want to know about the good and the bad.
Most bugs are identified quickly, and solutions are either underway or awaiting release. If you find a bug, please contact me with the details of the issue, I can then recreate the problem & fix it. The application should not consistently crash.
What other features are planed?
Whatever is suggested by you, the end user. I receive a lot of good suggestions, I can’t say they will all get done, but I do try and respond to all emails. Features that are requested the most and I can see merit in (i.e most useful) help set the development road map. So please, email me! malcolm@mbarclay.net
About Me
I spend most of my time in lead or senior contracting roles building all sorts of systems and applications on a number of technologies (Flex, Java, Objective-C, Web Scripting Languages and about 5 different database flavours). Feel free to email or give me a call. Mb. +44 (0)7515 357 232
Why is journey planning so slow!
This is down to the response time at the Transport for London journey planning server. On average it takes about 15 seconds to retrieve a set of journey plans.
London Bus retrieves all plans in one hit, this way once you have a set of journey plans as you select & view each one the application does not need to go back to the server again. This makes navigating & deciding on the best plan for you much faster.
The planing system will wait up to 2 minutes to get a journey plan; after that it will time out and you will need to try again. Journey planning is generally faster over a WiFi connection but it does work and has been throughly tested over Edge & 3G.
The TfL server will sometimes slow up at the beginning and end of each work day. Continue reading »