I hope Louie will survive this one.
Quick question, is this an actual app you are building/have built... or just a concept. I'm only asking because it feels pretty polished compared to most of the "unsolicited redesigns" that are so en vogue right now.
I'm not 100% sure you need to auto-scroll long attraction names. You show so many characters, I'd think if they ended in ... it would be totally fine and then you avoid the awkwardness of multiple rows animating at different times in a list you're trying to read.
Consider solid icons at top for back and favorite. This way they are most legible over photos and provide a larger perceived tap-area.
In the bottom nav, consider simply saying "Park", "Studios" and "Village". This way the text can be bumped up a little more (hard to read now). People who have this are THERE... so just those shortened names are enough for people to understand.
Also with the bottom nav, consider having the current "section" and rectangle indicator a darker/richer blue. This way its a bit more clear as you're running around in the park with this thing what section you are in. In general, tweaks like this will help people who are probably using this thing while walking or being distracted by kids.
Nice work man.
It's just a concept ;)
Thanks for the tips ! About attraction names and park names, I put myself in Disney marketing manager shoes who doesn't want to cut name or shorten them :P
LOVE the gloved hand for the back button, that's a wonderful detail. I will say, I expected a bit more magic for an app about Disneyland - a little more whimsy in the UI - as it's a bit sterile and strict, outside of the custom icons. But for a purpose-driven app, it's fantastic work.
Very text heavy and the font size looks a little small.
How does the user know to scroll horizontally between rides? Commonly a page control indicator is used.
The Tabs at the bottom all look like they are all in a highlighted state. Usually tabs are greyed out when unselected vs. using the bar over the top to indicate selection.
As an iOS developer I wouldn't recommend tabs at the top of the screen because the tap target of the back button/info button extends below it's rectangle on screen.
Otherwise nice job. It's so frustrating not knowing how long you might have to wait in line for a ride. Kudos on the gloved back button.