Skip to content

Conversation

@CDRussell
Copy link
Member

@CDRussell CDRussell commented Jul 11, 2018

Task/Issue URL: https://app.asana.com/0/72649045549333/715540186137137
Tech Design URL:
CC:

Description:
Adds a new variant for informing users they can add the DDG app as their default browser.

This time, it's a call to action on the new tab screen.

phone-portrait-keyboard-visible

Steps to test this PR:

Nougat or newer

  1. Perform fresh install; if you are given variant mu or mv; continue. if not, clear data and try again (or manually fiddle with the variants in VariantManager)
  2. Verify the new tab screen shows call to action.
  3. Click call to action, ensure you can see the default browser info activity and can navigate to settings
  4. Choose to make DDG the default browser; verify the button is no longer visible
  5. Repeat step 1.
  6. Click the X button; verify the button is no longer visible

Marshmallow or earlier

  1. Perform fresh install; verify you get the default variant key="" since we don't support these variants on pre-Nougat devices
  2. Verify you never see the call to action

Internal references:

Software Engineering Expectations
Technical Design Template

CDRussell added 22 commits June 15, 2018 14:56
…add_to_home_screen

# Conflicts:
#	app/src/main/java/com/duckduckgo/app/browser/BrowserTabFragment.kt
#	app/src/main/java/com/duckduckgo/app/browser/BrowserTabViewModel.kt
#	app/src/main/java/com/duckduckgo/app/global/ViewModelFactory.kt
These have slightly different requirements in terms of their scroll-observing behaviours. We do want the browser layout mode to respect the toolbar scrolling for instance, but we don't want the same behaviour for the new tab view. Trying to use the same `app:layout_behavior="@string/appbar_scrolling_view_behavior"` behaviour in both modes means that the new tab layout is essentially forced off screen vertically and it makes it difficult to add a button that anchors to the bottom.

Splitting these into two distinct modes lets us better control both modes without trying to find one set of views and flags which works well enough for both.
@CDRussell CDRussell requested review from brindy and subsymbolic July 11, 2018 11:13
@brindy
Copy link
Contributor

brindy commented Jul 17, 2018

On my One Plus One (Android 5.1.1), there's a faint flicker of the CTA just as the keyboard comes up.

Edit: I also see this on Nougat+ when the variant is such that the CTA shouldn't be seen.

Edit: Setting android:visibility="invisible" in the CTA container layout seems to fix it.

@brindy
Copy link
Contributor

brindy commented Jul 17, 2018

After clicking on "Go to Settings" and making DDG the Browser App, I then hit back to get back to the app CTA is not visible as expected, but the logo is missing.

screenshot_1531815783

Pixel 2 API 27 emulator.

@brindy brindy self-assigned this Jul 17, 2018
Copy link
Contributor

@brindy brindy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good apart from a couple of buggettes. :)

Copy link
Contributor

@brindy brindy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug seems fixed and I saw each of the variants. LGTM!

@CDRussell CDRussell merged commit 2316b5c into develop Jul 20, 2018
@CDRussell CDRussell deleted the feature/home_screen_call_to_action branch July 20, 2018 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants