Our designers use Figma but the licenses are so expensive that people on the product team can’t even make small changes or illustrate concepts. Additionally the UX has tons of hidden features making it hard for non experts to discover how to do simple things like export mockups.
As a result the designers have a backlog of small busy work changes instead of focusing on the key design questions. No one else has licenses to make updates or knows how to use the tool.
The product team has started using Whimsical which is easier to use and is more reasonably priced for people who only use it occasionally or need to quickly illustrate low fidelity concepts. Now we have two design tools to essentially get around UX and pricing problems.
It amazes me that there is no authentication provided by governments in the US to citizens. They just accept a social security number as if it was some sort of password, when it was never intended for that purpose. Other countries give citizens an electronic ID to authenticate themselves. It seems this would prevent hundreds of millions of dollars in fraud and identity theft.
I really hope you adopt the latest models particularly streaming attention variants. I think you should validate with users the assumption that latency is more important than WER.
IMHO the WER is more important than latency improvements in the millisecond range. The most frustrating thing is having to dictate over and over and the transcription is incorrect each time.
Consider that the time to a correct transcription is the latency plus error correction. If error correction is manual it will be orders of magnitude slower, so optimize for WER.
I’m terms of competition, Siri has latency in the 5+ second range due to the network call especially in area with poor data rates. I think a client side model like yours will easily win in this category. If you’re already ahead here, why not focus on WER next?
Another great capability is to generate alternative transcriptions for words with low confidence values to allow for quick error correction. Do you offer something like this today?
Also, consider the long term view that new models are constantly being released and refined. It’d be best to have an architecture that allows quick replacement without a lot of hand tuning, or where the tuning can be automated to a greater extent.
If PayPal wasn’t such a crap company they’d be the perfect solution for this problem. Just enter your payment and shipping info once and get one click checkout on any site.
This is pretty cool my biggest problem with micropayments is friction when browsing and friction for managing subscriptions. Integrating it into the browser should make it much more automatic.
It’s kind of a chicken and egg problem where publishers wont benefit until readers have it and vice versa. I hope this grant results in a killer app that generates some critical mass for the standard.
We recently started using another scaffold generator from http://scaffoldhub.io. It’s similar to this but geared more for apps than for marketing sites. It allows you to build out a complete data model and backend. It’s got a lot more features but they add complexity to the code that might not be needed for everyone.
As a result the designers have a backlog of small busy work changes instead of focusing on the key design questions. No one else has licenses to make updates or knows how to use the tool.
The product team has started using Whimsical which is easier to use and is more reasonably priced for people who only use it occasionally or need to quickly illustrate low fidelity concepts. Now we have two design tools to essentially get around UX and pricing problems.