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

feat: New landing page design #3079

Merged

Conversation

pranshuchittora
Copy link
Contributor

@pranshuchittora pranshuchittora commented May 23, 2021

Details

New landing page design

Fixed Issues

Closes #2938

Tests

QA Steps

  • Match the UI with the Figma Designs
  • Previously we are only showing Terms in the mobile. In the new design we are showing Terms as well as license.

Tested On

  • Web
  • Mobile Web
  • Desktop
  • iOS
  • Android

Screenshots

Web

Screenshot from 2021-07-08 02-18-44

Mobile Web

Screenshot from 2021-06-18 00-16-10

Desktop

Screenshot 2021-07-08 at 2 24 23 AM

iOS

Simulator Screen Shot - iPhone 12 - 2021-06-23 at 21 47 43

Android

Screenshot from 2021-06-18 00-18-11

@pranshuchittora pranshuchittora requested a review from a team as a code owner May 23, 2021 17:43
@MelvinBot MelvinBot requested review from Jag96 and removed request for a team May 23, 2021 17:44
@shawnborton
Copy link
Contributor

Looks like the mobile view should have more padding around the inner logo/UI/etc.

Copy link
Contributor

@Jag96 Jag96 left a comment

Choose a reason for hiding this comment

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

Conflicts and a few comments

paddingHorizontal: 24,
},

ph7: {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this used? If not, let's remove it and any other unused classes that have been added here. For example, we have ph2 and ph4 above but not ph3 since it isn't used.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ideally we should keep all the values even if they aren't used.
This won't increase the bundle size as unwanted objects will be tree shaken during compile time

Copy link
Contributor

Choose a reason for hiding this comment

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

Bundle size isn't the reason we want to avoid adding unused classes, the main reason is to avoid adding unnecessary code that can potentially be used by other contributors. In this case, we don't have a need for ph7, but if it is added in this PR then somebody could use ph7 later on and cause inconsistent styles across the app.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Copy link
Contributor

Choose a reason for hiding this comment

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

Were these removed? I still see them in the project now, it looks like 7-10 are unused after the latest changes.

@pranshuchittora
Copy link
Contributor Author

pranshuchittora commented May 29, 2021

Looks like the mobile view should have more padding around the inner logo/UI/etc.

Is that works?

Screenshot from 2021-05-29 12-04-34

fix: Linting issues and removes unwanted props

fix: minor styling changes

fix: Terms of service component change for native

feat: PR review changes and removed unwatned props
@pranshuchittora pranshuchittora force-pushed the pranshuchittora/feat/landing-design branch from 72f226c to 059a4d3 Compare May 29, 2021 07:46
Copy link
Contributor

@Jag96 Jag96 left a comment

Choose a reason for hiding this comment

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

Added a couple more comments, will let @shawnborton review the latest style

paddingHorizontal: 24,
},

ph7: {
Copy link
Contributor

Choose a reason for hiding this comment

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

Bundle size isn't the reason we want to avoid adding unused classes, the main reason is to avoid adding unnecessary code that can potentially be used by other contributors. In this case, we don't have a need for ph7, but if it is added in this PR then somebody could use ph7 later on and cause inconsistent styles across the app.

src/styles/styles.js Outdated Show resolved Hide resolved
src/pages/signin/TermsAndLicenses/index.native.js Outdated Show resolved Hide resolved
Jag96
Jag96 previously approved these changes Jun 2, 2021
Copy link
Contributor

@Jag96 Jag96 left a comment

Choose a reason for hiding this comment

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

This is looking good to me, good work on this! A few things for @shawnborton to check on since I'm not sure if they're real issues:

  1. Landscape iOS has a bunch of space at the top. Probably not an issue, but just double-checking w/ design
    image

  2. Web with a small window has some tight spacing on the left and bottom, again just double-checking w/ design
    image

Will leave final review to @shawnborton

@shawnborton
Copy link
Contributor

Sorry for the delay - hoping to review this tomorrow.

@pranshuchittora
Copy link
Contributor Author

Hi, @shawnborton any update on this?

@shawnborton
Copy link
Contributor

Sorry for the delay! Looking into this now, going to start adding design comments.

On desktop, the fine print does not have the same outer padding as the form above it:
image

@shawnborton
Copy link
Contributor

Do we need the padding on the bottom of Forgot?? Doing so makes a slight jump in the position of the input when you go from email to password:
image

@shawnborton
Copy link
Contributor

When the screen is in that weird middle size between mobile and desktop:
image

Let's actually make sure the content has a max-width and is just centered, like so:
image

@shawnborton
Copy link
Contributor

Expensify at the bottom of the sidebar should actually use a .svg and not be written in text:
image

You can use this file here and it should be shown at 78px wide: expensify-wordmark.svg.zip

@shawnborton
Copy link
Contributor

The sidebar itself should not be a fluid width on wide screens. I see you currently have it at 25%:
image

It should actually always be fixed at 375, the same as the sidebar width when you are signed into the app. Once we hit the responsive breakpoint where we hide the blue area on the right, then the sidebar should just be 100% wide.

@shawnborton
Copy link
Contributor

Just chiming in as well to say I agree with Joe's feedback about this:

Landscape iOS has a bunch of space at the top.

@shawnborton
Copy link
Contributor

Also just a heads up that I will be OOO next week, so tagging @michelle-thompson to help out with final design review while I am out.

@pranshuchittora
Copy link
Contributor Author

Do we need the padding on the bottom of Forgot?? Doing so makes a slight jump in the position of the input when you go from email to password:
image

There is no padding 🤔

@pranshuchittora
Copy link
Contributor Author

Landscape Compatibility and max width

Peek.2021-06-06.21-33.mp4

@stephanieelliott
Copy link
Contributor

Hey @Jag96 I think this is blocked on your review? We have a tight deadline for this one, can you take a look when you have a chance?

@michelle-thompson
Copy link
Contributor

There is no padding 🤔

As long as the input field doesn't move around when switching screens, that is what's important here.

And I think the landscape view on mobile looks good 👍

@pranshuchittora
Copy link
Contributor Author

@shawnborton I have updated the PR with the final changes.

Screenshot 2021-07-14 at 12 21 05 AM

@shawnborton
Copy link
Contributor

shawnborton commented Jul 13, 2021

Thanks for the update! Do you know what's happening with the fine print here? The line height looks strange:
image

And cc @kevinksullivan - should it be "New Expensify" or "new Expensify"?

@shawnborton
Copy link
Contributor

@pranshuchittora it also looks like you missed changing out Expensify.cash here:
image

@pranshuchittora
Copy link
Contributor Author

Done

Screenshot 2021-07-14 at 12 24 33 AM

@pranshuchittora
Copy link
Contributor Author

Wait somebody again changes the TermsWithLicenses 🤦🏼

@pranshuchittora
Copy link
Contributor Author

pranshuchittora commented Jul 13, 2021

Fixed, it was a file reference issue that occurred due to rebasing with the main.

Simulator Screen Shot - iPhone 12 - 2021-07-14 at 01 12 44

@@ -259,17 +259,26 @@ export default {
},
signInPage: {
expensifyDotCash: 'Expensify.cash',
expensifyIsOpenSource: 'Expensify.cash is open source',
expensifyIsOpenSource: 'New Expensify is open source',
Copy link
Contributor

Choose a reason for hiding this comment

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

@kevinksullivan is this how we want it to read? As stated elsewhere, this just seems clunky/grammatically incorrect to me.

Copy link
Contributor

Choose a reason for hiding this comment

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

Perhaps "The new Expensify is open source"?

@@ -95,7 +95,7 @@ export default {
hello: 'Hello',
phoneCountryCode: '1',
welcomeText: {
phrase1: 'With Expensify.cash, chat and payments are the same thing.',
phrase1: 'Welcome to new Expensify! Enter your phone or email to continue.',
Copy link
Contributor

Choose a reason for hiding this comment

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

This language is confusing. Perhaps 'Welcome to the new Expensify! Enter your phone number or email to continue.'

@kevinksullivan does it not seem weird to you to have it say "Welcome to new Expensify!"?

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree. I think the New Expensify is best as the latest mockup shows.

src/languages/en.js Show resolved Hide resolved
@pranshuchittora
Copy link
Contributor Author

@joelbettner I have updated the PR. cc @shawnborton

Screenshot 2021-07-14 at 2 21 56 AM

@shawnborton
Copy link
Contributor

@pranshuchittora Thank you - one last change - can you please capitalize the "N" in New Expensify?

@pranshuchittora
Copy link
Contributor Author

Done @shawnborton

Screenshot 2021-07-14 at 2 28 33 AM

Copy link
Contributor

@Jag96 Jag96 left a comment

Choose a reason for hiding this comment

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

LGTM!

@Jag96 Jag96 merged commit b9569af into Expensify:main Jul 14, 2021
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging in version: 1.0.77-6🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅

@isagoico
Copy link

Web - Profile - Too much space in mweb safari in log in page

Action Performed

  1. Go to staging.expensify.cash

Expected Result

Log in page should be displayed properly

Actual Result

Too much space in mweb safari in log in page

Build: 1.0.78-0

Notes/Images/Video
OS and browser used: Safari

@pranshuchittora
Copy link
Contributor Author

pranshuchittora commented Jul 15, 2021

This is the expected behaviour as per the provided design

image

@shawnborton
Copy link
Contributor

True, but I do think it would be nice if that top margin above the icon used a relative unit. Remember I left that comment here: #3079 (comment)

We have this in place on our Expensify.com homepage:
image

Where the top padding is 15vh. Perhaps we can create a follow up issue to make this a bit more mobile friendly. To clarify, I don't think this is a blocker for paying @pranshuchittora for the work that was completed, I just think we can separately follow up with some enhancements.

@OSBotify
Copy link
Contributor

🚀 Deployed to production in version: 1.0.79-4🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

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.

[HOLD for payment July 20] Design updates to the Expensify.cash login page