Skip to content
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

Responsive BottomSheet #71

Merged
merged 9 commits into from
Apr 8, 2020
Merged

Responsive BottomSheet #71

merged 9 commits into from
Apr 8, 2020

Conversation

tommypoa
Copy link
Contributor

@tommypoa tommypoa commented Apr 3, 2020

What's new in this PR

  • Replaced max snap point of the BottomSheet to be responsive to the height of the device
  • Not entirely pixel perfect (not sure what the repercussions of using percentages is as compared to the other option which is pts)

Relevant Links

  • NA

How to review

  • Responsiveness to different screens

Next steps

Tests Performed, Edge Cases

  • Checked responsiveness for devices of different screen sizes

Screenshots

CC: @wangannie

@tommypoa tommypoa requested a review from wangannie April 3, 2020 03:22
@tommypoa tommypoa changed the title [WIP] Responsive BottomSheet Responsive BottomSheet Apr 6, 2020
Copy link
Member

@wangannie wangannie left a comment

Choose a reason for hiding this comment

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

Small height change for the minimized version of the drawer but otherwise looking good!

Comment on lines 282 to 285

MapScreen.navigationOptions = {
headerShown: false,
};
Copy link
Member

Choose a reason for hiding this comment

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

Don't need this anymore -- I deleted these in a navigation clean up in #56

Copy link
Member

Choose a reason for hiding this comment

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

On second thought this will get removed in the merge

"files.associations": {
Copy link
Member

Choose a reason for hiding this comment

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

Wait these shouldn't be in here right..

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is strange - even though I inevitably caused these changes due to format on save (no way to turn it off somehow) but what I've changed it to is what is currently reflected in master so I'm hoping..that might be ok?

@@ -20,6 +20,9 @@ import {
SearchBar,
} from '../../styled/store';

const minSnapPoint = 300;
Copy link
Member

Choose a reason for hiding this comment

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

Were you going to comment/document how these were determined?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was going to, but the math does not really add up and was done largely by trial and error. Should I still have it down?

@@ -20,6 +20,9 @@ import {
SearchBar,
} from '../../styled/store';

const minSnapPoint = 300;
Copy link
Member

Choose a reason for hiding this comment

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

Also this should be a little higher. In Figma you should be able to peek the images https://www.figma.com/file/drhxZht9Mvogrc6aLn7MsK/Spring-20-DC-Central-Kitchen?node-id=7827%3A55

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed minSnapPoint to 325, which is a little higher (16px vs 11px in figma) but given that our current product cards do not have backgrounds, I gave it a little bump to show at least some parts of the product image. Feel free to change it to something that makes more sense in terms of design decision!

Copy link
Member

@wangannie wangannie left a comment

Choose a reason for hiding this comment

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

Looks great!

@wangannie
Copy link
Member

Added minimum snap point for map accessibility on really small phones like the iPhone SE.
Min

@wangannie wangannie merged commit e7c8a25 into master Apr 8, 2020
@wangannie wangannie deleted the tommy/responsive_bottomsheet branch April 8, 2020 18:49
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.

None yet

2 participants