So you are just creating fullscreen modals? I think you will get problems down the road. The user needs to know where he is, where he could go. I was already thinking about an fluid kinda interface like that. But i came to the conclusion that in reallty ist s different. Something like this might work for easy applications. But you will get problems from the developer perspective (caching, multithreading and other complicated stuff) as well as from the IA structure for your application.
...or she :)
Is the term "user" female? Wasn't aware of that.
where he is, or where he could go
"The user needs to know where they are, where they could go."
When talking about users, assume plural and speak about them as they, not he or she, unless you are targeting a single person specifically.
Thanks for this hint! I am terrible in writing english, but i still try my best.
Just do whatever you want, it's a comment on a dribble post.
Cool virtue signalling, great input.
I'm glad we could all come to a conclusion on scolding you for using the "he" word. SHAME ON YOU!
Thanks for the thoughts! yeah the app is geared towards both male and female users, not targeted at one more than the other - and we totally agree with your conclusions about a user needing to feel oriented in the app.
from my perspective as a designer, this was an attempt to break out of a traditional tabbed navigation at the bottom of the screen, but in reality it's not too dissimilar - just rearranged, and as our developer pointed out: it is interesting to pursue new patterns in regard to navigation but they can come at a cost if the user does not have a pleasant experience using the app because they were expecting something more familiar.
... this was an attempt to break out of a traditional tabbed navigation at the bottom of the screen ...
Why? The user will know this component and also knows how to use it. Something new might be offensive and more distracting than helping. Just creating something new doesn't mean it's better. Stick with things that the user know and create new components where there is no solutions for, easy as that.
Yeah, we agree with you Jan and had already come to that conclusion internally :) I'm passionate about exploring new things which is why I even conceived of trying out a new navigation. Right now in our project phase we are able to explore some less conventional ideas which is why I built this prototype in Principle for Mac. We as a company definitely value creating user centric experiences, but we also seek to try new approaches if we have the time and freedom to explore before we need to begin production. As others have pointed out here, there is value in thinking outside of convention. If we only believe there is one way of doing something, we as an industry will stagnate and overlook opportunities to bring users delight & better experiences. It's also challenge to our own team of engineer & designers to expand our capabilities through new problems. Thanks for all your feedback, I appreciate that you're very passionate about the topic.
Oh very nice I'll definitely check out Pasquale and his article! thanks for sharing!
Don't worry about people are saying here or in Dribbble... it means NOTHING.
- Make a prototype
- Test it with as many of your target users as you can
- Therein is the answer
The last step - before showing the client - is to run this past your devs to see how you might resolve some of the potential issues Jan Semler raised.
What is this commonsense you're speaking?! :D
Agreed with the other comments around functionality - but if we're not continuing to push the medium we're going to stagnate. Maybe not 100% in ALL cases, but there's likely a good use for this out there. Nice work.
Love the Navbar.
Interesting idea, but I feel like the title is a little misleading. Just because there isn't a clearly designated "navigation" bar or menu list, doesn't mean the UI is completely navigation-less.
Ah, sorry about that, it was meant to be cheeky-humor.
Well... this is exactly how snapchat is built.