-
Notifications
You must be signed in to change notification settings - Fork 15
Smartshehar dev
Live from the 357 in Worli.
1. The route buttons in the Routes tab should also be in Devnagari like on the Find tab.
2. The reverse directions in Journey tab seems to not be working.
3. Route numbers are being repeated on Routes tab for some reason -- is that because you are using the various rows in Atlas? The SMS route also sends a message with routes repeated.
4. The stop buttons on Find tab are *great*, much easier to tap. But they should not be on the stop name, they should be equal sized buttons with icons left justified, which match the size and feel of the route buttons in the list below. You could perhaps also make the names selectable like before (though they should be black, not blue, to fit the style of the route list, which could also be selectable on the names as well as button).
5. Note the new field "chowki" in BEST StopMaster which Ghogare recently sent. We should have different colour stop icons on the buttons for those which are chowki (terminus) or not. These are not only depots but also intermediary stops on every route. These are also major exchange points between routes.
6. The Schedule button to the right of the route button on the Find tab is a fine idea, but it would look cleaner if it were right justified. In general buttons are better located on the left and right sides of the screen where one's fingers rest and can easily tap. I like the pop-up function to get the full schedule, I hope we can make this time-sensitive based on frequency calculations from Atlas so the button shows a time on it but when tapped shows the whole schedule.
7. Following the same logic, you could also make the metre distance info in the Stops Near You list into right justified buttons with the metre distance in them. When pressed they take you to that stop in the Map tab.
8. As I noted earlier and others gave feedback on the list, when the app defaults to a location, or when a new stop location is manually selected from the list, some signal or message must be given to the user. It's still not inuitive that tapping on a stop button/name makes that your default From, and when location is automatically refreshing can be yet more disorienting.
9. Based on feedback on this list, the Clear button on Find tab is also a bit unintuitive. Firstly, whenever anyone is entering text they use an on-screen or real qwerty keyboard where they can delete an entire line by doing alt-delete. You have to reach up to hit Clear from the keyboard if you want to use it, or keep hitting delete until *all* the text clears. This is painful whether you use your keyboard or the Clear button I suggest that pressing delete should clear the *entire string*, and leave the drop-down menu with the suggested stops for the string just deleted.
10. Also the Find button on the Find tab also works counter to the keyboard user, in that even after one selects From and To stops you must reach up to hit Find. You should just be able to press enter on the keyboard, or better, when the auto-complete is completed it should just query the route without further input from the user.
11. The recent stops buttons are nice, but they still keep disappearing when I rotate my screen or switch between tabs. 12. If you can implement the modifications to Clear and Find in 9 and 10 above, I think it would be simpler to have only one button for recent stops on top, and put the Find button below it where the second recent stops button is. You could make both buttons a bit bigger and give them icons, one could the same stop icon used in 4 above for Recent Stops, and one could be a new icon for Find.
13. Assuming you agree with the above, then there is really no need for a Clear button and you free the space currently occupied by the clunky Clear and Find buttons. To answer the dilemma of how to clear the From or To without opening the keyboard (which I hate to do when I'm waiting for the bus, buttons are way better), I suggest you use the Android back button to clear From or To.
14. The above solution also fixes one of my biggest issues which is that the Android back button quits the app if it is invoked on the Find tab. Whereas on other tabs it takes you back to the last viewed tab. I am always quitting by mistake when I hit back, and sometimes I would rather do that than reaching up to hit the Find tab to start a new session.
15. When no location is found a default stop like Hutatma Chowk should be auto-filled so the user is not confused when they first start the app. They should at least see the Routes list, not just an empty tab with just From and To.
Refer to 207 onwards now
1. We should have buttons for stops on Find and Journey tabs, with the railway-type icon. Tapping it on Find tab fills in the stop in From text field and changes the list of Routes below. Tapping it in Journey list takes you back to Find tab with same behaviour. Perhaps later we can style these stop button icons differently for depots and big junctions and more minor stops. -- 207 has buttons
2. Also when a new stop is selected on Find and the list of routes at that stop is refreshed, the user needs some signal, like a quick status/activity message. It's just not obvious right now that tapping on a stop name resets the name in the From field. Stop buttons and status message will help signal to the user, but they should not slow things down. -- Toast is shown
3. The list of stops in Journey tab still needs a lot of improvement. The stop names should be a little larger and maybe bolder than their area names. The distances should be right justified. And there should be buttons for the stops. -- We have to come up with what we need. I am revamping the screens one at a time. We are on the routes tab now.
4. The app crashes if the user enters gibberish text in To field on Find tab. This needs to be fixed by giving an error or Stop not Found message. -- Doesn't crash in 207
5. I still find that overhanging panel on the Journey tab which you can hide/show to be largely redundant since, except for the route number, all the other info displayed in that panel is also in the list below. I know you added the hide/show in Settings just for me, but I want to be able to hide it while still knowing the route number. I think -- We can decide what to show/hide
6. I've been thinking about the colour scheme, and think we could make the Find, Routes and Journey tabs look and feel more like the signature colours of BEST: wintergreen, light olive, steel grey and post office red. If you are open to adjusting the pastel background colours of the lists please let me know and I will send the colour codes. -- My main goal is that colors should be easily visible especially in sunlight
7. When I need to enter text manually in the text box on Routes tab, it would be *so much better* if I could have a numerical dialpad (like a phone dialer) than the default Android keyboard, since I *always* have to either open my physical keyboard or switch to numbers on the on-screen keyboard. For L, C, AC, AS buses the autocomplete list will be find once the user has entered the route number. -- I have to figure out if we can narrow the keyboard to a set of keys, that would be ideal
8. As we discussed on the phone, the version/build number *must* be included in the app info inside Android and not just in the apk file name. This helps in reporting and versioning between users who have installed older versions (especially as we transition to builds #200+ with the new and old dbs) and also because filenames are often not entirely visible inside Astro or other Android file browsers. -- I have been doing that now. Have also reduced the name size so that its easy to see.
On the 5 inching slowly through Bhuleshwar.
1. On the Journey tab the "At: stop name" is no longer required now that the currently located stop is at the top of the list. Redundant, get rid of it.
2. You could perhaps move this to the Map tab, and perhaps on the bottom of the tab, not the top. I like how it centers to current location, but the user needs a cue to what stop they are looking at. Also you could perhaps zoom in more to current location.
3. On Map tab, can you remove the straight lines between stops in a route? This further masks the errors in our geodata collection, and also those lines are just ugly and not useful, if someone wants to know the sequence of stops they can switch back to the Journey tab.
4. I asked for this before, let us have buttons on Journey tab for every stop, left justified and styled like the route number buttons are on Find and Route tabs. Also other layout and formatting improvements I suggested for Journey tab remain to do.
5. Further to 3. above, it would also be nice on the Journey, Route and Find tab stop lists to have a button right justified which takes you to that location on the Map tab. In fact this was a feature of your very first app which would be great to bring back now that we have OSM in the Map tab.
6. The app loads and launches much faster now, so perhaps the pulsating logo doesn't make sense any longer, since the animation is hardly begun before the app is ready to use. Make it solid. This was a nice idea anyway, sorry to be so demanding. :)
7. The bug I noted earlier in landscape mode on Find tab where the Recent Stop menu selector occupies half the width of the screen and has the text Select Recent Stop persists. It should only have that arrow and the From and To fields show have flexible width when rotated.
8. On Routes tab, the radio buttons should not be left justified, they should be evenly spaced across the width of the screen and be flexible for portrait and landscape. Also they should read "Regular", "Limited", "Corridor", "AS/AC", "AC Express" with the full names and in that order, not as you have it now. This more closely follows the BEST's own nomenclature and is clearer.
9. Following on 8., there's no point in the "All" radio button since that's the default setting for the menu, either add "Regular" after all in the radio buttons or eliminate it altogether and have no buttons selected by default. I think this is more intuitive.
10. On Routes tab, I still cannot press "Enter" to show a route after manually entering the number. It just does a carriage break, which is useless. Also if I have a number of routes suggested as I begin typing and tap on that list entry, that should be the same as tapping "Show Route" or hitting Enter.
11. On the Routes tab, the "Show Route" button width should be exactly the same size as the text entry box. And this should resize on rotation.
1. The buttons for Routes on Find tab should not spill over into two lines if the route code is too long. This often happens with route codes more than three digits and almost always happens for AC and AS buses. It screws up the flow, and the buttons are ugly.
2. On Find tab, "Stops near (lat-lon)" should read "Stops Near lat-lon" without parentheses around it, and with W and N after lon and lat.
3. On the Routes tab, when lists of indirect bus routes are displayed in conjunction with a train journey or walk to nearby stop, just comma separated lists, not live buttons. We want buttons and lists like on the Find tab or like on Routes tab when there are multiple direct bus routes -- however long this makes the list. This is important. The user is left to manual entry for indirect routing otherwise.
4. On the Journey tab we need more distinction of the way the bus stops entries are formatted for easy visual reckoning. Make the stop names larger, right justify the distances in metres for stops, remove the parentheses and comma at the end of the metre distance for area/stations below it.
5. The buttons for route codes on Find tab and in direct bus routes on Route tab is a great concept, and as I suggested before I think we should have buttons for Nearby Stops with the generic railway stop icon designed by Arvind Lodaya.
6. Similarly we could have buttons for stops in the Journey tab, which when pressed return the user to the Find tab with that stop entered in From.
7. A variation on the above, which would be similar to the function we have already coded in the SMS app with the "stop" handler, is pressing the stop button on the Journey tab takes you to the Routes tab, with all the bus routes at that particular stop displayed as a list (with buttons for routes of course).
8. Launch time for the app is still painfully slow compared to pre-175 build versions. Also now what is happening is the location is still "not found" when the Find tab appears, there is a pause, and then my location is fixed and lists and entries appear.
9. In build version 180 yesterday I found that when location is not found after several queries the whole app becomes unusable, entries and lists disappeared from Find and Routes and Journey stays stuck on the last selected. I'm concerned generally about the app being too dependent on location fixity. It should be usable by people who want to keep their GPS and geoip lookups permanently off, for privacy or other reasons.
10. I also find the toast message "waiting for location" hovering too frequently, have you changed the frequency of location fixes? Often the message lingers or even hangs until another tab is selected. This is annoying and especially so when I need quick fast info on demand, and I can't see what's behind that message. I say just remove it, we already signal status fairly well in tab transitions.
11. Also the "Refresh Location" button inside the Android menu doesn't seem to work. I am right now near Charni Road and whether I manually refresh or I get the status message "waiting for location", the Find tab still shows me at Nehru Planetarium. BUT the Journey tab shows me near SK Patil Udyan, which is CORRECT. So there's something wrong with
12. Please note that in all the above cases my GPS is off. I never turn it on unless I am doing tracking or mapping, and rely on geoip network location. This works extremely well and the app doesn't need GPS, which often doesn't work inside the bus unless you are in line of sight of a window.
13. On the Routes tab there's still that ugly useless empty coloured fields when no route has been searched or found. This should all go and the tab should just have the bus route selector list and radio buttons.
14. On the Find tab when I rotate my screen the Select Recent Stop buttons next to From and To show the text "Select Re" and the rest is cut off. They should show the arrows. Or they could have icons in future, it's a nifty and useful feature that is still a bit difficult to see is there.
15. The Android menu does not appear when on the Routes, Journey or Map tabs. I can only access it while on the Find tab. This needs to be fixed. Also let's have some icons for those buttons, we can refine them later on with help from Chitra or Arvind.
From the Virar Fast train en route to Andheri then Yari Road, now on the 251.
I just encountered failures in route lookup, I'm not sure if this is a bug in your database or in the app, I suspect the former but maybe that is also causing the app to behave badly.
1. Try to find From Andheri Station W To Versova-Yari Road, I cannot select the To stop as the name expands to "versovavesaveyariroadbusstationvesaveyariroadbusstation". Try this and see if it's a flaw in your data entry. Anyway a short name should never be this long. :) Even if I remove the duplicate-double error, it still shows nothing on Routes tab.
2. A workaround for this was to have Andheri Station in From and manually inspect the list of Routes at this stop, which shows 221, 249, and 251 as direct routes. But tapping on 221, 249 or 251 on Find tab (or looking them up manually on Routes tab) either does nothing, or if I selected another route earlier it just shows that route in the Journey tab, not the one I selected.
3. Is this data for these routes missing or is the stop name error noted above screwing things behind the scenes? Even after force stop, clear data, relaunch of app I cannot see any of these routes/journeys.
4. I also noticed a distinct delay in trying to switch to my Home screen after doing 1. above, there was a long pause with black screen. This behaviour is consistent after repeating 1. several times.
5. Ultimately I confirmed the buses between Andheri Station and Versova by SMS! In ChaloBEST SMS, where we also use your short names for now, the same stop is "vesave-yariroadbussstation". Is the bug in 1. because of the hyphen, or preceding every shortname with the areaname in the Droid app? I know it's hard to do, but I really think displaying the short names in the Droid app is ugly.
6. On Find tab when I typed "yari" in the From text entry box, it did not find Yari Road Bus St, only when I typed "verso" did it auto-suggest Versova stops and I could select the correct stop name. Are you actually searching the whole stop name for auto-suggest or only some part of it? Or is this due to the flaw in the data entry suggested in 1.?
Sorry been unwell for the past two days and not on the bus. Now on the 2 L from Mahim to Delisle Road.
1. The bigger buttons on Find tab are fine in portrait mode, but too high in landscape mode, can you make them shorter?
2. The bigger problem is the much larger text below in the list of Nearby Stops, it's become too big now (I know I asked for it bigger). Large text makes for easier tap and select, but also for overflow. I would *much* prefer the button style you have used for the Routes list below. Can you make buttons of similar dimensions as the ones below with the railway stop icons on them? Then you could reduce the text size a but while still making the list items easy to tap/select.
3. On the Find tab the drop down lists of Recent Stops next to From and To text fields do not render in portrait view, there is only blank space on the right side where they should be. They render in landscape and if I switch back to portrait they disappear. When I switch back again they disappear, or sometimes take up half the width of the landscape view.
4. On Find tab, your removal of the header from the Nearby Stops list makes it unclear what that list is. It saves space, but is confusing for a new user. Maybe it could just say Nearby Stops at the current Lat-Lon? It's a bit geeky but cool, explains the logic of the list and the metre accuracy to the right of the stop names below.
5. On Find tab, both headers for Nearby Stops at... and Routes at... lists can be much smaller text, to save space, also because they are static text and not links. Same size as current route list text, but bold perhaps.
6. Not displaying the full route of a bus on the Journey tab is proving painful for me as a commuter. One benefits from knowing the full extent of the route, not just the stops between From and To. I suggested a solution of shading From and To stops on Journey tab as green and red respectively, and keeping the currently located stop as blue.
7. Further to last on Journey tab, I also think it would help to center on the current location after briefly displaying the header and then scrolling down automatically (the old app did something like this). Right now you assume that my current location is also my From stop, which is not always true. I may be somewhere else entirely and want to find out about other routes/journeys.
8. I am experiencing crashes again when launching the app (only sometimes) and when switching to it by long press on Home when in another app (again only sometimes). I will try and isolate behaviour and gather logs for when this happens next.
9. Loading the app seems to take much more time now, why? The pulsating logo is very nice! But maybe the red logo can stay static and only the halos pulsate? Also if it takes more than ten seconds perhaps we should have several status messages so the user doesn't get impatient (i.e. Loading ChaloBEST..., Finding your location..., Launching app...).
10. If one selects the Routes tab when there are no query results, one just sees a lot of blank space and static text "Near buses" and "Trains". This should be hidden unless actual route query results and only show the routes list with the radio buttons below.
11. Still waiting for you to make the Map tab to center on my current location. It will make this feature vastly more useful than now (and cover our asses where the geodata has errors). It shouldn't be too much work, it seems to be a standard API function in apps that use OSMDroid. This would also make the Map tab to the Journey tab which I hope will also center on my current stop (see 7 above).
Begun on the 38 this morning in Mahim, now on the 521 headed to Worli. More feedback:
1. Pressing any of the buttons for routes in the list on the Find tab causes force close. Please check this. The same behaviour is not there when tapping a route number button from Routes tab, it goes to Journey as it should.
2. I'm still getting crashes on launch that can only be fixed by force stop to the app, clear data, and relaunch. Even then after one or two sessions it crashes on opening again, or does even weirder stuff like default to Find tab with all boxes, buttons and lists blank and the ChaloBEST logo on top. Force stop...
3. Crashes or resets also seem to happen when I switch to landscape mode, I think especially on Route tab which resets when I do this. Again I must force stop, clear data, relaunch to get the app working again. I nearly just got run over in Khodadad Circle because I was debugging this one while scrambling to catch a bus.
4. The splash screen is great to see again, but could you nudge the logo upwards so that it is not blocked by the status indicator below in portrait view. I realise this is not possible in landscape mode.
5. Also I thought we could try an animated logo where the logo is inside the status box, and replace the spinning circle with the logo with its halo waves changing colours to indicate the app is working? Just an idea to keep in mind.
6. I don't like the new and improved To and From fields and Clear and Search buttons. The buttons are too small to tap, space is wasted between them, and neither the input fields nor buttons have flexible width for landscape view.
7. On Find tab the Stops Near You and Routes at Start list titles should be much smaller text.
8. Also in both list titles the stop and area in mentioned, which is wasteful and redundant. My suggestion is to have the first list "Stops in x" where x is the currently located area name, and put the nearest stop as the first entry in the list and also auto-fill in the From field. In the second list it should say "Buses at y" where y is the nearest stop detected and auto-filled in From. Don't put the area proximity for the stop in the title bar, it will already be in the first list on the right side.
9. Also make the stop names in the first list larger and easier to tap, much like the bus routes in the second list which now have buttons which are visually and physically easier to detect and tap. Maybe we should have buttons or icons for them (the one which Arvind designed which has the blue circle with red stripe like railway station signs would work). I need to be able to tap these as easily as the route numbers, since I want to explore all my options from nearby stops.
10. The route selector list with radio buttons you have implemented on the Routes tab doesn't seem to work yet, the list is blank. Also it would be good to have the text entry box and show route button as on the Find tab. There's a strong argument for removing these functions from the Find tab altogether, now that the Route tab both has these static lists as well as dynamic routing information when you do a From-To query on the Find tab.
11. There is still too much space between the text entry box and show route buttons in this list, and off center positioning when viewed in landscape. Just make the text entry box occupy the left half and the show route button the right half of the screen. This kills dead space and makes the box and button easier to tap.
12. The display of information on Journey tab is very confusing. Make the stop names larger and bolder than the area names, separate the metre distances into columns and right justify them. It would be great to be able to tap on the stop names and be sent back to the Routes tab with all routes at that stop listed, or to the Find tab with that stop auto-filled in From. Or we can put buttons or icons which do that.
13. As I requested earlier, the Map tab when selected should centre on the user's current location rather than the entire map of the route, which is too zoomed out to be useful (and exposes many errors in our geocoding!).
Live from the 168 at Dawn Mill Naka.
I cleared data before uninstalling and reinstalling 159 and it seems to be stable now, am trying to get it to crash but can't yet. Will let you know. Some further feedback:
1. On the Journey tab can you center on the current location highlighted in blue, as in the earlier non-native app?
2. Rounded corners for all tabs would be much nicer on the eyes. As close as possible in look and feel to the Android dialer/contacts default app.
3. In Find tab landscape view there is too much whitespace in the Buses Near You list between the frequency in minutes and the start-end stopnames. It would be nice if these names could be in one span in landscape, and two spans in portrait view.
4. Reiterating my request on Route tab to have the topmost route info in one span and not two, saves space.
5. On the route tab under Direct Buses the timings given don't make much sense. Once we get the app connected to the BEST scheduling, we must have this information there, right now maybe you just want the same start-end stopnames as in the list on the Find tab.
6. On the Map tab one can see that for almost every journey, one or more of the stops has been incorrectly geocoded, so some stops are north of Virar or out in the Arabian Sea. :) This is again a database issue we will deal with separately in future, for now I suggest the initial bounding box of the map view should be the user's current location, rather than the whole journey. This anyway zooms out too far to be intelligible, and exposes errors in our data.
7. Is the tracking of user's location working in this app? Is it phoning home with logs of IP, location, accuracy, etc.? If so, perhaps an check box on the Journey tab to confirm the user is actually riding that bus at the time would help in refining user-contributed rider location in the logs.
8. If logging does work, can you send me a link to this feed? We can host this on the chalobest server or configure a subdomain such as log.chalobest.in. I want to analyse and visualise these logs using georss and geojson feeds. We can have live tracking on an OSM web map eventually for opt-in users.
Feedback live from the 151 in Worli Naka.
1. If I tap on a stopname in Journey tab, it would be nice for it to take me back to the Find tab with that stopname entered for From. Also it would be nice to have a button right justified to take me to the stop on the Map tab (it should zoom to stop location in OSM if lat-lon is available).
2. When I press the back button my phone, it always quits the app. It would be more intuitive if it took me to the previously viewed tab instead. Only if no tab was previously viewed/cache in the session should it quit on hitting the back button.
3. In the Find tab, the To text entry box appears slightly wider than the From box. They should be evenly sized. Also the text boxes both spill over and mask the nifty drop down which lists recent stops.
4. When I get autocomplete suggestions in From or To in Find tab, to select them by tapping I must tap on the actual text, not the cell/whitespace in the list. The latter is more convenient for selecting since it means you can tap the whole width of the list entry. Right now it requires a few tries each time.
5. I love the buttons around the bus numbers, and the colour coding red for Limited buses. How about darkish green for Corridor, navy blue for AS, and dark purple for AC Express? Also you could make the text size larger and/or bolder since the margin between the text and button edge is too much now.
6. When one hits "Enter" on keypad in route text entry box on Find tab, it gives a carriage return, it should be the same as tapping "Show Route" button.
7. On Routes tab the from-to route printed at very top should be in one single line, not broken into two lines. Saves space.
8. I would prefer if the text and list in Journey tab is black on white like the rest of the tabs, it looks more consistent.
9. In the Find tab, the list of routes is show the Start and End points separated by a hyphen printed continuously, almost always spilling into two lines. It would be cleaner and nicer if the Start stop was printed with a "to " or hyphen on the first line, and the End stop printed on the second line. Just need a carriage return after "to " or the hyphen.
Live from the C-52 in Chembur.
1. Tapping on map tab when no route has been earlier selected causes the app to quit unexpectedly.
2. When I switch from portrait to landscape view on my phone either with accelorometer or opening my keyboard, the app does not redraw for the new screen dimension, it re-initialises (splash screen) and then quits unexpectedly.
3. Can you make the From and To text input boxes on Find Tab flexible so they take up entire width of the screen.
4. Are you using short names in the From and To fields? They are very ugly! Since we have all that space we should get the full stop names in there.
5. I do not like when a From-To query returns my journey without the entire bus route displayed -- it seems to only show the stops between From and To, which is not helpful and can be confusing. The user should be able to see the entire bus route and we can distinguish From and To stops by colour, logically green and red, as also present location, blue.
6. Noted earlier -- love the splash screen but the initialising message obstructs the view! Can it be moved up or down?