ljuba / transporter-iphone Goto Github PK

...either by upping the resolution of the maps generated on the Transporter-Server (https://github.com/ljuba/Transporter-Server) or by using a MapView in the Directions view controller.

allow users of the iphone app to "zoom in" and explore details of the transit routes.

This needs to go along with OTA updates since we don't want to be downloading tons of static map images over 3G. Ideally, the map, once loaded, will be stored in a cache so that next time that bitmap can be shown instead.

This is a big one and will require changes to the Transporter-Server (https://github.com/ljuba/Transporter-Server), but it would be great to tap on a stop in Near Me and see the paths of each of the bus lines that stop there.

Currently, when you tap "Edit" the grab handles cover the favorites cells. The cells should be narrowed slightly to let the handle be seen more clearly.

I'd like to restructure the app to resemble the iPhone music app, where the tab bar at the bottom isn't visible when you're on the StopDetails screen. That way, you'd have room for a button bar on the bottom of the StopDetails screen, which could be for other features.

Hello, my name is Jim Nielsen. I run iOS Icon Gallery a website devoted to showcasing beautiful icon designs from the iOS ecosystem. I am working with the amazing icon designer Michael Flarup to create a book showcasing the art of iOS icon design. You can read more about the project at https://www.appiconbook.com/

The reason I am reaching out to you is we would be flattered to include the Transporter icon in our book.

Let me know if you'd be interested in working with us to get your artwork in our book and I will provide more details.

This requires doing an audit of the code that's already there, building tests for it, integrating with the server code to check for the latest version of the transit data, etc.

Currently, the app uses a flashing Google-style pin to indicate that a bus/train is arriving. I think we can do better.

Someone should put the app through Instruments and see where there is room to improve performance of the app. I've never done this before and I think there might be some obvious things that could be improved.

This could be done in small type in each row of the StopDetails screen for BART stops.

I'm pretty sure the algorithm for determining the position of the bus/train within a line is shitty and buggy. I'd love someone to take a look at it and possibly rewrite it.

Currently, the favorites screen doesn't reuse cells in its tableviewcontroller. This is because each cell might be a different height (owing to a different number of bus/train lines that might be favorited at a stop). As a result, scrolling is choppy.

@sfmta_muni on twitter posts notices when there are service disruptions or improvements.
one possible improvement to the transporter app would be integration of this muni twitter feed.
knowing about disruptions enables us to plan our trips better.

The images used by the segmented control overlap in strange ways because the standard segmentedControl isn't meant to have custom images for each segment. The custom segmentedControl should be a collection of UIButtons and should support any number of buttons.

All of the Market Street Subway stations coincide with large clusters of surface transit stops. To make it easier to select the right stop, we should add configuration to show a different icon for the underground stations.

Both MUNI and AC Transit are returning errors.

The data in platforms.xml is there to help group the BART train lines on the stopDetails screen by platform. So all trains stoping on Platform 1 are shown in the platform 1 section.

This data was gathered by hand from the real time arrivals API on the BART website. This data may be out of date and should be checked. Also, a script could be written to update these values over time. This should probably be done in the Transporter-Server project.