<!-- See https://github.com/Microsoft/calculator/blob/master/docs/NewFeatureProcess.md for suggestions on how to write a good feature pitch. Just want to submit an idea quickly? Try Feedback Hub instead: https://insider.windows.com/en-us/fb/?contextid=130 --> **Problem Statement** The app UI is currently outdated and could be better in sync with the Windows 11 Calculator. **Evidence or User Insights** <!-- Why should we do this? Potential sources of data: Feedback Hub, other GitHub issues, other anecdotes from listening to customers in person or online, request from another team, telemetry data, user research, market or competitive research --> **Proposal** <!-- How will the solution/feature help us solve the problem? How will it meet the target audience’s needs? If there are business goals or metrics, how does this improve them? --> **Goals** <!-- What you want to accomplish with this feature. Typical examples include "User Can *perform some task*" --> **Non-Goals** <!-- Things we are explicitly not doing or supporting or that are out of scope, including reasons why. --> **Low-Fidelity Concept** <!-- Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage. -->
Problem Statement
The app UI is currently outdated and could be better in sync with the Windows 11 Calculator.
Evidence or User Insights
Proposal
Goals
Non-Goals
Low-Fidelity Concept