microsoft / microsoft/calculator
Investigate launch performance issues
@joseartrivera is already working on this.
Since Apr 24, 2020.
- Dominant language
- C#
- Stars
- 31.1k
- Forks
- 5.8k
- PR merge metrics
- No merged PRs in 30d
Description
Launch the app. It takes about a second to start. This means you almost certainly lose input if you start typing right away (especially if you have a "calculator" button).
Steps To Reproduce
- Press calculator button on keyboard.
- Immediately start typing 2+2 on numpad (as an example.. whatever it is you're trying to calculate).
- A second later calculator launches
- You will probably have lost at least the first 2, and maybe also the + and second 2, because the app didn't launch fast enough.
- Result: you have to press the button and consciously wait (feels like an eternity) for the app to start before you can do what you wanted to do.
Expected behavior
Calculator should launch fast enough that you can just start typing the thing you're trying to calculate after pressing the calculator button (maybe around 100ms or so).
Device and Application Information (please complete the following information):
- OS Build: 10 0 16299 0
- Architecture: X64
- Application Version: latest master
UPDATE: This issue is now being used to track recommendations, observations, and investigations into how we can improve the actual and/or perceived launch performance of the app. Any actionable ideas that are identified should be broken out into their own issue for tracking purposes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.