togakangaroo / coa-nolahealth-mobile

Code For America HackDay Nola Health Mobile app
3 stars 3 forks source link

'Back' navigation from Search/Detail pages #6

Closed rcschafer closed 12 years ago

rcschafer commented 12 years ago

Reported by Frank Sullivan

Add a ‘back’ button to the titlebar at the top of the search results & provider detail pages.

togakangaroo commented 12 years ago

Do we really need this? What is wrong with using the browser's back bar?

rcschafer commented 12 years ago

After looking around it seems that while many mobile-optimized sites implement their own navigation interfaces the practice is somewhat frowned upon. There's ways to hide the browser controls in Mobile Safari but there's lots of caveats and I doubt it works on all mobile browsers.

I'd rather rely on the built-in navigation than get into rolling our own controls. We could add a Back button to the header and see how it looks but I think the important thing is to not HAVE to have a custom Back button. As far as I can tell, the app doesn't require this (unlike some that have form-driven navigation.)

togakangaroo commented 12 years ago

Yup, one of the nicest things about jquery mobile is that it handles hash-tag navigation for you, including back-button support.

On Tue, Feb 28, 2012 at 8:46 AM, rcschafer < reply@reply.github.com

wrote:

After looking around it seems that while many mobile-optimized sites implement their own navigation interfaces the practice is somewhat frowned upon. There's ways to hide the browser controls in Mobile Safari but there's lots of caveats and I doubt it works on all mobile browsers.

I'd rather rely on the built-in navigation than get into rolling our own controls. We could add a Back button to the header and see how it looks but I think the important thing is to not HAVE to have a custom Back button. As far as I can tell, the app doesn't require this (unlike some that have form-driven navigation.)


Reply to this email directly or view it on GitHub:

https://github.com/togakangaroo/coa-nolahealth-mobile/issues/6#issuecomment-4217035