Mon, Sep 17
The task was to create this prototype (B) for testing against prototype A (T195335). Testing completed in T196398 indicated a preference for the incremental improvements in Prototype A.
As such, this task and associated tickets can be closed pending further exploration of nav improvements in future.
Hi @Dbrant - just one thing missing - the user should be able to mark Notificaitons in Archived as Unread (as per web)
hi @Dbrant - just noticed a minor UI item in the Settings, the separator lines in the mock are missing:
LGTM on 2.7.239-alpha-2018-09-07
This bug is specific to Prototype B
Fri, Sep 7
Sorry @Aborba - I placed in QA Signoff first, all these tickeyd haven't been through Design Signoff yet.
Hi @Aborba - should be request an account and link to the Request account page in the Task description
Hi @Dbrant - font sizes and weight are fixed, but the color of inputted text should be the 'Material theme Primary' color once filled (and 'Material theme Disabled/De-emphasised' when hint text)
Thu, Sep 6
Ahh that is not ideal. @cooltey @Dbrant , can we use an existing timestamp component rather than this custom one? The main thing is to show a timestamp of last synced, the nitty gritty of the display style just needs to be adaptable to local language display formats.
Wed, Sep 5
Hi @Dbrant - in addition to the outstanding visual design items in the above comment, some other initial comments from user testing:
hi @cooltey - this format ostensibly seems fine as long as the time stamp is shown, however you may want to check with @Dbrant, since different languages have different ways of showing time and date formats.
Thu, Aug 30
thanks @Sharvaniharan - think it's looking good so far!
Tue, Aug 28
sure @Sharvaniharan, but please note from the animated gif that the animation is not of a white arrow and line over a separate grey circle that turns blue, but rather a *single* icon which is a grey circle with a cut-out arrow and line that turns blue.
Mon, Aug 27
@Charlotte & @Mikhail - just fyi this was the placeholder ticket i'd created for testing the Notifications feature.
Fri, Aug 24
Thanks @cooltey - just checked the APK and looks great!
Thu, Aug 23
hi @Sharvaniharan - would be great if you can send me the most up-to-date APK in the meantime whilst posting to the releases page is worked out. thanks!
hi @cooltey - I just tried the latest version of prototype 1 and neither update is showing (shadow is still shown under tabs, no floating queue on a single reading list)
Looks fixed on 2.7.239-alpha-2018-08-22
Wed, Aug 22
Hi @cooltey, moving to the bottom (with 8dp padding) is preferable, but just having it remain visible is the main thing thanks!
hi @Sharvaniharan – please also confirm that the changes you've made on this ticket are merged into the prototype for testing at http://releases.wikimedia.org/mobile/android/wikipedia/scratch/app-alpha-prototype_2.apk
Also also @Sharvaniharan - can the prototype be updated here please: https://releases.wikimedia.org/mobile/android/wikipedia/scratch/app-alpha-prototype_2.apk ? The current linked app does not have your recent fixed to the tab bar implemented.
hi @Sharvaniharan - just running through the script and realized that the article top toolbar is actually incomplete:
|Expected- top right exposed icons are add to reading list and share||Actual:- still showing just the search icon|
Hey @cooltey - an unrelated interaction issue that I just noticed is that the floating queue element is not visible over a reading list. It is expected that the Floating queue element remains visible over a single reading list as well.
Tue, Aug 21
Since T150459 is now resolved, it should be relatively simple to implement this task.
Closing as we are tracking the individual suggestions under the Android-app-feature-Description-Editing tag
hi @Dbrant - can we add the tooltip as outlined in this ticket and close?
hi @cooltey - can you clarify what it means for some of the items that are not done? It's just that if it means "won't be done" due to constraints mentioned then the piecemeal changes don't really work. For example, I would not want part (e) drop-shadow under the tab title bar if part (d) and (b) is not possible, since the drop-shadow just makes it more obvious that the tab bar is a separate object to the tab content area.
Mon, Aug 20
hi @eranroz - as far as I am aware there has not been specific discussion, as both apps have not used a border for a while now on thumbnail images, nor on mobile web:
|Thumbnail on mobile web||Thumbnail on Android search results|
The intended behavior should be as per Expected in the task description, therefore this is a bug and not design debt.
This is not a design-debt item, but rather a bug that appears in certain OS versions (presumably 5.1.1 and below).
The Android and iOS app both do not have a border on thumbnail images, this is as intended.
LGTM on Pixel 2 (8.1) Wikipedia v2.7.239-alpha-2018-08-17
Aug 17 2018
Hi @cooltey - the screenshot still shows the sharp corners for the left top and bottom parts of the queue element (where the image thumbnail is), and I am not a fan of the semi-transparency. If it is not possible to add rounded corners I would rather we reduce the width of the floating queue element by 16dp as an alternative way to get it to stand up more from the cards.
Aug 16 2018
hi @cooltey - this is almost perfect but there are still a few minor visual discrepancies between the Actual vs Expected:
hi @cooltey - thanks for fixing the shadow, it looks good now! A couple of ever so minor quibbles still:
hi @Dbrant - just checking if these updates are in-progress?