-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New main screen UI in v3.0 #2843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I tried to follow this specification for mockups, but here are some problems I faced:
After we have a bottom bar, keeping a global action bar for all screens reduces the area when considering the actions belong to each screen. Ie. Exploring have an search field, which I really like, on toolbar. Adding a global toolbar means shifting search field one row bottom and this means reducing our usable area (Or adding the action to existing global toolbar, I didn't find this solution simple). Thus I am not in favor with having a global toolbar. Both limited connection mode and notifications can be accessed from home bottom bar item. We can indicate notifications with a red dot on upper right corner of home icon. How does that sounds @misaochan ? |
@misaochan I am not sure about moving upload button under home, I think we should keep on contributions page instead. Or we can have it on both home and contributions screens? |
@neslihanturan , I made a rough sketch of how I envisioned Home to look like. The bottom bar you made with Nearby and Explore looks great to me, so I just copied it onto my sketch. :) A few points to note:
Sounds good to me |
Thanks @misaochan , I think I got what is in your mind. |
Hi, we had a discussion about usage of nav drawer together with bottom navigator.
On the other hand we have several items on our current nav drawer and it can be hard to fit all of them in home screen. Proposed solutions:
What do you say? Do you have other suggestions? |
To find the best approach for our new UI, we may need to sort our current and to have features:
Account related things:
Accessible from other screens:
Plans
The motivation for using a bottom navigation in our new UI is presenting Explore as one of main features. So our must bottom items, currently 4:
The limitation for use of bottom navigator is max number of items we can have is 5, according to design guidelines. As I listed above we have several items and it is hard (and not user friendly) to fit all into one screen, home. We can't keep navigation drawer with bottom navigator since this is not recommended. Based on this information we should decide: 1. Use a fifth item on bottom navigator
2. Use a menu on toolbar of home fragmentIn this option I suggest having 4 bottom items and adding account related tasks under a menu which is accessible from the toolbar of home fragment, ie. a three dots menu.
3. Do we really want to use bottom navigator?I know bottom navigator is very cool but we may have too many features. We should consider if bottom navigator really fits with our app or not. Please join to the discussion. |
Yes, this is a bit of a dilemma. It would be great to get more thoughts on this. @nicolas-raoul ? I think that that Option 1, the 5-item bottom nav bar, should be reasonably future-proof. We would likely be able to fit most things under those 5 items - for instance if we gamify Nearby, we would just add it to Nearby, not to the main nav bar. But it does pose a restriction somewhat, and also it would be more difficult for users to navigate since it is a huge change compared to my initial proposal (just using the bottom nav bar as a shortcut and keeping the nav drawer). Also I am not sure how it would appear on small screens, 5 items is a lot. For Question 3, it feels like a step back to go back to pure nav drawer. We currently have tabs that encourage users to focus on Nearby. If we go back to pure nav drawer, we lose the ability to highlight our main features. However, ditching the bottom navigator may indeed be the safest option. Conclusion: I am undecided and hoping for more input, especially from regular users. :) |
Sorry I haven't got much time to read this thread and the next three weeks will be super-busy too... anyway I am sure you will make good decisions :-) |
https://phabricator.wikimedia.org/T223159 has design suggestions by Robin Schoenbaechler, the designer whom we worked with at the hackathon. The (unstable) WIP PR is #2972 |
Thanks for remembering it @misaochan , it looks really helpful. |
Copy pasting the design posted by @neslihanturan at #746 (comment) for reference. It looks good to me personally. Opinions appreciated. :) |
That certainly does look nice. Just wondering, is this going to be the how the re-design would look? Or is there more work to it? |
That is a mockup for how the redesign would look, yes. I imagine we might discover that some tweaks might be necessary when implementation starts. |
Actually, now that I think about it... I love the cloud icon and it should stay, but additionally I think we need a very clear way of telling the user that limited connection mode is on. With this design a user might accidentally turn the mode on, and then they might just not look at the upper right of their screen and wonder why things aren't working the way they are supposed to. Maybe even having text somewhere that says "Limited connection mode ON" (with a tooltip) if the mode is enabled, could be beneficial. |
I know it is only a draft, but if I had a comment to make, it would be to add a bit of space before the next picture, or remove a bit of space above the picture name. Taking the Instagram app as a reference, I can see that the vertical spacing between two posts is double the size of the vertical spacings that can be found within an individual post. |
Yeah, certainly. This reminds me of the "Offline library" feature that the Wikipedia app had in its alpha but was paused before it went into production. They had a nice design which clearly indicated when the user was browsing offline and online. I guess we could do something like that here. Here's a task related to that design: https://phabricator.wikimedia.org/T163595 |
That looks like a nice design! Thumbs up from me. :) |
The Wikipedia app recently pushed a change to its alpha version in which it has a bottom nav bar similar to the one found in the proposed design. Just wanted to mention it in case someone wants to get an idea of how having the "More" menu in the bottom nav bar would feel like in live action :) |
* Add additional classes from 2019 hackathon implementation * Make first tab work * Make explore tab work * Handle back button for contrib and nearby * Fix framelayout and nav bar allignment * Fix nav bar tint * Fix nearby card layout * Make contributions number visible * Change menu icon according to fragment * Make notification icon work and remove drawer * Make favourites accessible from nav bar * Turn bookmark and explore activities into fragments * Use bottom sheet instead of more fragment * Add actions * Remove unused classes * Fix indentation * remove more fragment title * Fix explore fragment indentation * Make toolbar settings as we wanted * Set card view styles * Make colors for explore actiivty * Remove drawer from achievements activity * Add back button to achievements activity * remove drawer from review activity * Remove drawer from settings activity * Remove drawer from about activity * Fix dagger injection of fragment * Implement skip login version * Add theme missing colors * Add style to moresheet * refactor name * call login with button * Remove all old bookmarks activity dependency * Make explore tab items clickable * Do nothing if same tab is selected * Fix notification icon color for dark theme * Fix wrong drawable colors * Handle back button after media details is visible from contrib and explore fragments * make favourites open media details * Fix profile icon * Make user name visible instead * Move user back to contrib fragment * Remove NavigationBaseAvticity * Fix typo in bookmark fragment * Fix menu button colors * Remove explore activity * remove drawer and dependencies * Make bookmark media details visible * Cleanup code * Code cleanup * Remove unused layout * Make contriblist UI look like in mockups * Change limited connecton toggle * Move list menu item to nearby fragment * Fix search button crash * Make media detail appear * Back button added * Fix back button npe * Change bookmark list view * Fix always the firs item displayed issue * Allign contrib list bottom line to simple drawee bottom * fix fragment string * Fix back button for mobile uploads * Make lists appear * Make fav item selected * Make favourites clickable * Add back button to media details * Add toolbar of notification activity * Change contributions icon * Fix card UI * Fix back button in explore * Make card views look similar to mockups * Solve campaign bug visible issue * Make borders a little softer
This task was mentioned in our PG proposal and is slated for the end of our grant, but I forgot to create an issue for it. :) Copying over from the proposal:
After the new features have been completed, we would like to tie everything together in a new main screen UI. Since the creation of the app, the focal point of the main screen has been the user's past contributions. However, the app is now very different from what it was at the beginning - we have the Nearby feature, an Achievements screen with a level badge and upload stats, a Notifications screen with user talk messages, an Explore screen that lets users browse other Commons photos, and various other conveniences. At the end of 2018 we will be able to display news about an ongoing campaign. And at the end of this proposed grant, we will have a limited connection mode, the option to pause and resume image uploads, and a "to-do" system.
When the time comes, we will create a few different mockups and seek community feedback on which one they like best, before proceeding with implementation. However, as a rough guide, a possible plan for a new main screen UI is outlined below.
The action bar (the blue bar at the top of the screen) could have:
A bottom navigation bar could have:
Home (which will be the new main screen) could contain:
All of this will culminate in the release of v3.0 of the app at the end of the project.
The text was updated successfully, but these errors were encountered: