cyclestreets / ios Goto Github PK

The namefinder entries currently have the same size/font text for both the street and context parts. So York Street, Cambridge (which is a combination of two XML fields in the API), appears all as the same text. Instead, the 'Cambridge' part should be smaller, and the comma can then go.

Needs prototyping of potential layouts. Ideally keep the same number of results, i.e. avoid having bigger boxes.

Long text should be shrunk instead of scrolled off-screen.

Show metadata as: [streetname]\n([streettype], [distance]) e.g. Newmarket Road\n(Road, 0.893km). This should also free up space so the menu should be shown.

I haven't tried the update in the field yet but I'm disappointed that the type for the info overlay is now much smaller. For long-sighted users this now takes it just out of visibility, which means I can no longer use it easily on my handlebar mount. Pity. Please boost size up again. I also regret the slight transparency of the info overlay- which was useful. It would help if you could max the map size to remove the top bar in use.

Make the walking sections be dashed line rather than solid whenever the line is drawn (i.e. main route page and itinerary).

NB The quietest route strategy currently tends to give rather more walking than it should. This is an area being addressed in the API side, but is complex and so is taking time to address.

Settings page map selection boxes could be cleaned up a bit, e.g. black corners.

Currently, if you are on the itinerary listing mode, and click on geolocation, the dot (representing user's current location) may be outside the currently-displayed map segment.

If switching on the geolocation button, ideally pan out so that the current location and the two points are both shown.

This is the master ticket for the addition of a full sat-nav mode rather than a journey planner app.

Key issues are:

• Retain itinerary mode?
• Show 'Turn left' rather than individual route sections
• Is the iPhone GPS fast enough to recognise the user's location?
• How to deal with "Take the fourth sideroad on the left"

Voice synthesis of road names will cost money (we obtained a quote around March 2010) so this might need a user paid-for upgrade to cover this cost, with the basic app remaining free. Obviously navigation without road names would be pre-recorded.

Currently the login action is only possible when the focus is in the final input box. This is awkward because it's not obvious to the user, and means that correction to a mistyped (but not previously noticed) username having already put the password in means going back to the password field to be able to submit.

It would be useful to be able to send occasional messages to users, e.g. that CycleStreets needs votes for a funding award, etc.

Needs API provisioning but that should not be hard.

Generation 3+ of the iPhone presumably saves the bearing into the EXIF tags. It would be good if this could be added into the XML API call, as the main site takes account of bearings when doing Photos-en-route.

Add iPad compatibility, which would mean:

• Different screen layout to maximise map size
• Technical changes to switch this on in the code

Please add other changes as comments against this ticket

Similar to #26, there should be a 'Tweet this photo' mode.

The credits section needs scrollbars and/or an 'Open in Safari' link.

Basically would be a box within 'My Saved Journeys' that expects a number and strategy type (balanced being default, and the other three shown); when entered, the journey is then retrieved via the API:

http://www.cyclestreets.net/api/#switchRoutes

When obtained, it is saved and then just becomes like any other route saved, i.e. retrievable/deletable.

Routes do not currently have an elevation profile, which is necessary in some areas of the UK.

Unfortunately the profile graphic used on the main site cannot be used as that is basically just an API call to Google Charts. So an ObjectiveC library would need to be found/written. The data is present in the API.

Currently the signin on the app only applies to the Photomap. Instead it should also appear as a standalone screen under 'More', so that when signed in, the journeys get associated with that username when going to the main site.

This would need some minor additions to the API to enable the username/password to be supplied, which infers a POST operation to the HTTPS side.

After uploading a photo, the photo number is shown in a modal dialog.

It would be helpful if there was some way to have this copied to the clipboard, for easy pasting into a twitter message etc.

Pattern is
http://www.cyclestreets.net/location//
where is the photo number

Not all itinerary lines have an icon

'Other' could have a 'Latest news' section, basically just a view of the blog as RSS.

Recent searches should be saved by default into a third tab, with the standard apple swipe-to-delete UI enabled to allow their deletion.

"Recent" should simply dumps in the results and underlying lat/long, with most recent at the top. If the user then starts typing at the top, it should revert to either Local or National, whichever was last used of the two.

At present, it is difficult to compare different potential routes, as this requires going to the settings screen and then replotting the start/end points. In practice this is not likely to be a huge issue as most users will probably prefer a certain type of strategy (probably balanced) then leave it as that.

There needs to be a UI way of switching between them immediately.

This also needs a change to the API, so that instead of supplying a new set of start/finish lat-long points, the itinerary ID is supplied instead, and the API then fills in the previously-unplanned strategy.

The unplanned strategies could be planned in the background if the user is not doing anything else in the app.

Click in (i) in the itinerary, and the map attribution notice stays in the middle.

Several people have requested the ability to add a GPX file. Although there are other apps for this, it would be a nice addition for the sake of completeness.

Needs to have an auto-sleeping option.

Suggested in feedback 2421.

Ability to name saved routes, so i could call something 'home to xxx'

The three-taps UI is innovative and quick once learnt, but is non-standard compared to other apps which use a drop-pin method. At present the first run has a set of dialogs to mitigate this, but their existence points to deficiencies in the current implementation.

The current system works on the basis of a tap to set start point, tap for end, then plan. The user has to work through these in that order, and the X button is effectively a 'go back one change' button.

One user report mentioned that the text in the centre of the top bar was assumed to be a button, and the user later realised it was guide text.

A decision needs to be made whether to keep this or move to a set of boxes in which the start and end point can be independently set, rather than have to work through them in order as at present but which requires fewer clicks and is more direct.

One possibility which retains the current quick three-taps system is for two icons on the top bar to represent the Start and Finish points, which changes state (e.g. with a tick) once filled in, so it's more obvious to the user that the itinerary planning is not complete until a certain point.

Photomap should use the icons on the main site, i.e. different icon for each category. See this URL for example:

http://cambridge.cyclestreets.net/photomap/

However, they should still appear within the nice blue marker box for clarity.

Should be able to go to a contact in the address book to enable 'Cycle to my friend' usage.

The user can pinch-out to zoom to an excessive degree - it is possible to zoom to an extent where the whole screen's display is larger than the width of a single road.

The zoom should be limited so that the most zoomed-in-level in the tileset is the maximum zoom available.

Signin screen: 'Login' is used in two locations, rather than 'Signin'.

CycleStreets house style is to use Signin as the term.

Have the blue dot follow the user on the main screen, as per the itinerary screen. Issue of battery life is crucial though.

Perhaps save this issue until full satnav mode is implemented.

The (i) button is not intuitive - should instead be an X or expand/contract button near the text

Map tile caching along line of plan: should start pre-caching (downloading) when no other downloading.

Need to check with tile provider acceptable use policy before doing this.

Should be a setting to enable/disable this, to save bandwidth.

Better text directions, e.g.: "Cycle for 20 metres then turn left", and "Turn left after ..."

This is a problem at the API end, not the app end but it may have knock-on consequences for app design to make better use of such data.

Perhaps this could be achieved using a 'flip for info' UI

Menu disappears when using the itinerary mode

CycleStreets feedback #4785 rightly complains that the photos-en-route can't be disabled in the itinerary view, which can prevent the road names being visible.

The use case is that you've planned a journey, done a bit, moved the map to find the current position, then close it again. Opening up again it is very useful to have that position still there.

Occasionally, after doing a search (e.g. for York Street), then immediately starting a new search phrase instead (e.g. Thoday Street), the results for York Street will flash up again.

A new search should always completely terminate the previous search text.

So the user can view all photos they have added.

Same as http://www.cyclestreets.net/photos/mine/ basically.

Needs API provisioning also, but this will not be hard.

The current 'fat circle' is not as nice as the purple pulsating circle that Google use. The latter also gives a better indication of the accuracy level at the time of that geolocation hit.

Several requests to be able to configure the distance units.

When in the photo mode within itinerary, it is possible to enable the keyboard to come up, even though there is no editable text.

User in main site feedback 2424 suggests making the GPS position clearer, particularly when using a handlebar mount. Notes that the Atlas app uses a big circular crosshair, which is much better.

A user asks (in main site feedback 2422):

"Can your iPhone app have an option to turn up the backlight? I have my iPhone mounted on my bike in the Biologic case and (as is common for cases) it covers the ambient light sensor.

So the phone's auto brightness makes the phone screen very dim. This occurs every time you wake the phone up. Is there a way to add a config option for the app to always make the screen always bright, ignoring the auto-brightness setting?"

CycleStreets has a places API which will be expanded to include things like restaurants, cycle parking, cafés, cinemas, tourist destinations, and really any kind of place that will be useful to cyclists. It will be done as a set of categories, with click-through to a category revealing the nearest locations of things in that category.

The app should implement this directory, with clicking on an entry pre-filling the destination point.

The settings section includes an option to switch between full/320px upload size.

A third option, which should be the default, should be added: "Upload full when using Wifi".

When planning a route, the start/finish point saved in 'My saved routes' should use the typed text rather than the exact response of the namefinder.

See also issue #40.

Can feel like it's crashed.

The existing photo picker is used because the OS version doesn't supply the geolocation EXIF tags. However, it is believed that OS4.1 fixes that.

So the application should use the native one for 4.1 and above, and the current one for below that.