Problem Statement
Calculator doesn't use enough RAM. If we migrated it to Electron, it could use up 1GB of RAM.
Evidence or User Insights
I went out and asked random people in public if they wanted their calculator to use up more RAM and 10 people said yes.
Proposal
It will solve the problem of the current version being too lightweight. It increases the metric of RAM consumption, which is good. Especially considering the start menu, you clearly need higher RAM usage so that you can superimpose an 8GB RAM minimum requirement.
Goals
It accomplishes the goal of pushing further in Microsoft's current direction. "The higher the RAM usage, the better."
Non-Goals
You must NOT support Win32 APIs. Too lightweight.
Additionally, you need to use Edge WebView 2 to ensure that it does not use excessive disk space. (If you do it right, it'll take less disk space than before and makes Edge WebView 2 a critical requirement, which are 2 pros. I see no downsides.)
Low-Fidelity Concept
Don't copy that design blow-for-blow (for obvious reasons) but take a page out of Google's book and make it simple and easy like that.
Requested Assignment
I would be willing to implement the web side of things,
but I am completely unwilling to touch the messy Win32 or
Edge WebView 2 APIs.
Problem Statement
Calculator doesn't use enough RAM. If we migrated it to Electron, it could use up 1GB of RAM.
Evidence or User Insights
I went out and asked random people in public if they wanted their calculator to use up more RAM and 10 people said yes.
Proposal
It will solve the problem of the current version being too lightweight. It increases the metric of RAM consumption, which is good. Especially considering the start menu, you clearly need higher RAM usage so that you can superimpose an 8GB RAM minimum requirement.
Goals
It accomplishes the goal of pushing further in Microsoft's current direction. "The higher the RAM usage, the better."
Non-Goals
You must NOT support Win32 APIs. Too lightweight.
Additionally, you need to use Edge WebView 2 to ensure that it does not use excessive disk space. (If you do it right, it'll take less disk space than before and makes Edge WebView 2 a critical requirement, which are 2 pros. I see no downsides.)
Low-Fidelity Concept
Don't copy that design blow-for-blow (for obvious reasons) but take a page out of Google's book and make it simple and easy like that.
Requested Assignment
I would be willing to implement the web side of things,
but I am completely unwilling to touch the messy Win32 or
Edge WebView 2 APIs.