-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add splash screen on web and desktop #12334
Add splash screen on web and desktop #12334
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use webpack plugin to inline the script for us and have the script in the separate file?
npmjs.com/package/html-inline-script-webpack-plugin
We could, but I think this JS is simple/standard/small enough that it will work on any browser that's modern enough for us to care about. So I'd say probably don't worry about it
web/index.html
Outdated
@@ -47,6 +47,26 @@ | |||
::-ms-reveal { | |||
display: none; | |||
} | |||
@media screen and (min-width: 768px) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move this stuff to web/index.css
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is index.css inlined?
web/index.html
Outdated
@@ -58,5 +78,31 @@ | |||
<body> | |||
<div style="position: absolute; top: 0; left: 0; right: 0; height: 30px;" id="drag-area"></div> | |||
<div id="root"></div> | |||
<div id="splash" style="position: absolute; top: 0; left: 0; right: 0; background-color: white; width: 100%; height: 100%; display: flex; justify-content: center; align-items: center;"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please move these styles to the css file mentioned in a previous comment instead of using inline styles.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
web/index.html
Outdated
@@ -58,5 +78,31 @@ | |||
<body> | |||
<div style="position: absolute; top: 0; left: 0; right: 0; height: 30px;" id="drag-area"></div> | |||
<div id="root"></div> | |||
<div id="splash" style="position: absolute; top: 0; left: 0; right: 0; background-color: white; width: 100%; height: 100%; display: flex; justify-content: center; align-items: center;"> | |||
<div class="splash-logo"> | |||
<svg fill="none" width="100%" viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we not use assets/images/new-expensify.svg
here instead (and ideally the logo for the correct environment)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather just inline svg because of performance, again if we don't have webpack inlining this for us.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same question, how much performance gain do we get by inlining the svg?
web/index.html
Outdated
</div> | ||
</div> | ||
<script> | ||
var minMilisecondsToWait = 1.5 * 1000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why using var
instead of const
and/or let
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Browser compatibility mainly. If we don't care about it, i can migrate.
web/index.html
Outdated
</svg> | ||
</div> | ||
</div> | ||
<script> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any reason we shouldn't:
- Move this JS code to another file,
web/index.js
- Then move this script tag to the header w/ the
defer
attribute
I think that gives us a few benefits:
- The HTML and JS are split into smaller files and downloaded in parallel, which should make them both available faster than if they're part of the same larger file.
- The JS code can be separated out
- The script tag can live in the header instead of the bottom of the file (not critical, but nice for html organization)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think those optimizations are fair in general but for the splash use case I think we need this small script inlined so browser does not need to fetch since we need to run this script as soon as we can on bootstrap
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vladamx how many ms does inline scripts shave off?
Co-authored-by: Rory Abraham <47436092+roryabraham@users.noreply.github.com>
…m/vladamx/App into vladamx-splash-screen-web-desktop
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, actually I think I'm convinced that inlining this stuff makes sense for the very specific use-case of a splash screen. While some of this code is a bit "ugly" to look at (i.e: inlined svg, var
in the inline script, etc...), the best fix for that would probably be to use webpack to inject that stuff inline, like @vladamx said.
So now I'm torn about whether setting up that stuff in webpack is worth it 🤔 On one hand it feels maybe over-engineered, on the other hand feels like a clean solution (and more consistent with other code in this repo)
@vladamx @rushatgabhane What do you think? Should we just leave this as-is or implement https://www.npmjs.com/package/html-inline-script-webpack-plugin and https://www.npmjs.com/package/html-inline-css-webpack-plugin ? |
replied in issue to implement webpack-plugin |
@roryabraham Updated. This is the inlined output |
@vladamx can you please help me trigger the splash screen I tried
Screen.Recording.2022-11-09.at.4.07.32.AM.mov |
@rushatgabhane Hm, I've just tested again and it seems to work fine on my side. Can you restart the server and if it persists can you provide some logs from the console or network tab if any? Screen.Recording.2022-11-08.at.23.49.51.mov |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, very clever with the resourceQuery
and resolve alias! Also, I've got a diff in package-lock.json
when I run npm i
– can you check if that needs to be committed please?
@roryabraham Updated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM and tests well 👍🏼
web/splash/splash.css
Outdated
display: flex; | ||
justify-content: center; | ||
align-items: center; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NAB missing newline at EOF
All yours @rushatgabhane |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Svg had its own sizing i needed to overwrite with higher specificity selector |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, all yours @rushatgabhane
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vladamx thanks for the changes!
@roryabraham LGTM as well
Web
Screen.Recording.2022-11-13.at.12.06.32.PM.mov
mWeb
Screen.Recording.2022-11-13.at.12.09.23.PM.mov
iOS
Android
Desktop
Screen.Recording.2022-11-13.at.12.04.46.PM.mov
PR Reviewer Checklist
- I have verified the author checklist is complete (all boxes are checked off).
- I verified the correct issue is linked in the
### Fixed Issues
section above - I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the
Tests
section - I verified the steps for Staging and/or Production testing are in the
QA steps
section - I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I verified the steps for local testing are in the
- I checked that screenshots or videos are included for tests on all platforms
- I included screenshots or videos for tests on all platforms
- I verified tests pass on all platforms & I tested again on:
- iOS / native
- Android / native
- iOS / Safari
- Android / Chrome
- MacOS / Chrome
- MacOS / Desktop
- If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
- I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
toggleReport
and notonIconClick
). - I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product was added in all
src/languages/*
files - I verified any copy / text that was added to the app is correct English and approved by marketing by adding the
Waiting for Copy
label for a copy review on the original GH to get the correct copy. - I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in
STYLE.md
) were followed
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
- If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- I verified that this PR follows the guidelines as stated in the Review Guidelines
- I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like
Avatar
, I verified the components usingAvatar
have been tested & I retested again) - I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
- If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a
/** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor) - Any internal methods bound to
this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
) - All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
- If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e.
StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)
- If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like
Avatar
is modified, I verified thatAvatar
is working as expected in all cases) - If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
- I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @roryabraham in version: 1.2.28-0 🚀
|
🚀 Deployed to staging by @roryabraham in version: 1.2.28-0 🚀
|
Just coming full circle here, this PR caused a regression. It worked on dev but not staging and production. We could have prevented this regression by locally testing staging and production builds. We generally don't do that on all PRs, but it's usually a good idea when changing code in the |
🚀 Deployed to production by @roryabraham in version: 1.2.28-2 🚀
|
Details
Since startup on web and desktop is not instant we want to avoid having long blank screen while app is starting up. This is especially visible when resources are not cached and network is slow.
Instead, we want to show a splash screen similar to the native mobile experience we already have.
The idea is to show the splash after specified minimum display time(avoids junk) and then wait for React to mount the root element with content, which will replace the splash screen with app content.
Open questions: @roryabraham
https://www.npmjs.com/package/html-inline-script-webpack-plugin
UI Responsivness Preview:
Screen.Recording.2022-10-28.at.21.23.13.mov
Fixed Issues
$ #12234
$ #12234 (comment)
QA / Tests
PR Review Checklist
PR Author Checklist
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
filesWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
).src/languages/*
filesWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
have been tested & I retested again)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)Screenshots
Web
Screen.Recording.2022-10-28.at.21.24.54.mov
Mobile Web - Chrome
Screen.Recording.2022-11-01.at.12.55.14.mov
Mobile Web - Safari
Screen.Recording.2022-11-01.at.12.53.35.mov
Desktop
Screen.Recording.2022-11-01.at.12.58.24.mov
iOS
Not affected
Android
Not affected