SML: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 4: | Line 4: | ||
It enables developers to create more intelligent email applications that can understand and act on the content of messages, rather than just treating them as plain text. | It enables developers to create more intelligent email applications that can understand and act on the content of messages, rather than just treating them as plain text. | ||
What is currently done via email, but manually? How can we automate it? | |||
What is currently not done by email, but whatsapp etc? What could be done, what nobody does right now? | |||
Feel free to add on the list! | |||
= Brainstorm Use cases and UI representation = | = Brainstorm Use cases and UI representation = | ||
Examples of possible use cases for SML: | Examples of possible use cases for SML: | ||
* Polls | |||
* Finding a meeting time that suits most people, or the most important participants. UI: Could show my calendar appointements at the proposed times. Optionally deny all proposals where I have a conflicting appointment. | |||
* Location tracking UI: show on map. Possibly with trace (past locations) and direction (where heading). Open in Google maps, allowing me to route there. | |||
* Email verification Button does http call, no browser page then deletes message | |||
* Invoice, order confirmation sent to accounting application puts products and price in a database of pitched products | |||
* Delivery notification when linked to order and/or invoice by ID, can show overall status of each ordered product , including order, delivery status, dates, price, etc currently scattered in at least 4 emails. | |||
* | |||