wordpress-mobile / wordpress-mobile/WordPress-Android

Quickstart snackbar duration seems somewhat short thinking of a user exploring/learning the Ui

Open
#20,110 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Enhancement Quick Start
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

Internal ref: p1706831477920259?thread_ts=1706821601.141289&cid=C01CW1VMLAF-slack-C01CW1VMLAF

Actual behavior

Thinking of the quickstart as a guided tour the fact the snackbar with the quickstart messaging disappears after a (short) duration, might make the user not being able to properly read the step rationale while exploring/learning the UI.

We might want to at least extend the duration by which the snackbar is presented to the user.

Steps to reproduce the behavior
  • go over any step of the quickstart
  • check the snackbar with the messaging description of the step disappear after a somewhat short duration
Tested on [S23], Android [Android 14], JPAndroid / WPAndroid [#20103 at 2ce97ec71e2b3317ed2bc3c115c32647f2eb759d]

Noting that increasing the snackbar duration seems worth, it was brought up though and I agree (see the linked internal ref) that makes sense to review the quickstart structure and flow overall since currently (cc @AjeshRPai 🙇 )

quick start is tightly coupled with the views and we need to think about a new implementation which is less coupled and scalable

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the quickstart on Android and observing how long the snackbar remains visible during each step. Review the quickstart structure and flow, including its coupling with views, then determine whether the agreed outcome is an increased duration or a broader scalable implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.