Use voice input in calculator

[iamgmujtaba]

There are many keyboards which don't have Numpad. So add voice assistant to use in the calculator. the result can be in text or in voice.

Problem Statement

it is very difficult for many users to use a calculator without numpad. In addition, there are many users wants to use calculator using voice assistant. In the future, even a blind person can use a calculator without any hesitation.

Evidence or User Insights

Proposal

Cortona is already enabled in the windows. in use case scenario, a user can say "hey Cortona open basic calculator. add five and seven and then multiply with nine." the voice assistant can tell the answer in voice and text. Furthermore, the result can be upload to other applications.

In the best scenario, you should make an API that can be used in the calculator instead of implemented from scratch.

Goals

• Input using the voice assistant
• The result should be based on text and voice
• Share/upload the results in other application like excel/word

Non-Goals

Low-Fidelity Concept

[grochocki]

Thanks for the feature suggestion! This does sound like an interesting idea. We have a process in place for feature suggestions that impact the end-user experience, which includes a template that helps frame the feature pitch. Please update using that template.

[iamgmujtaba]

Thank you for interest. I could not find the template. I would love to add this new feature in the calculator.
Best Regards

[HowardWolosky]

@liquidworld - the template is in the issue you filed. You just didn't fill it out. It's discussed more in the documentation that @grochocki linked to.

[MicrosoftIssueBot]

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

[abcasada]

@liquidworld you can hit the edit button on your post, above, and fill out the sections (Problem Statement, Evidence or User Insights, etc.)

[ghost]

Multiple terms could also be valid for a single action where applicable and/or practical, to make it more flexible. For example, Show, Complete, Result, Enter, Finish and Equals could all work the same to show the final result.

[iamgmujtaba]

@liquidworld - the template is in the issue you filed. You just didn't fill it out. It's discussed more in the documentation that @grochocki linked to.

Hi, @HowardWolosky I have updated the use case. If you want any more help then let me know.
Regards.

[grochocki]

We reviewed the pitch and would love to move forward with it! I think this pitch is a great start, but there are still some open questions. Moving this into planning to iron out some of the details.

There are varying degrees of support we should consider. For example:

• Basic (e.g., “three plus four equals”)
• Moderate (e.g., “what is 500 meters in feet?”)
• Advanced (e.g., “plot a circle centered on the origin with a radius of 6”)

We also would think through all the options for how we expose this to the user (e.g., should there be a dedicated button?).

I created calculator-specs/voiceInput to track progress. For more information on next steps, check out our spec workflow.

[iamgmujtaba]

I am glad to hear that the pith is selected for pre-production.
I would recommend first implement basic option for different support. Here are my suggestions.

• Basic ( User first input operation then number. eg. "Multiply five and two" or "Add six and three" or "open scientific calculator")
• Moderate ( e.g. "convert 500 into feet" or "calculate my date of birth in current date")

Most of the users are very aware of their privacy issue after Facebook problem. I also think the button for voice assistant is a very good idea. In addition, to update the user about voice assistant working the skin color of header of the calculator little bit changes. To update user he/she using the voice assistant.

I believe you can improve Cortona user input actions as for each individual user uses the calculator or other tools.

[mcooley]

Have we considered text-based natural language input for calculator? I often do calculations by typing expressions directly into the Windows or Bing search bar, e.g. “(4 + 2) * 8” or “square root of 25”. However, I think native support in the Calculator app would be an improvement over a web search engine. For example, we could support offline usage. Adding support for text-based entry of natural language calculations would be independently useful, and the underlying logic could be reused for handling voice input.