3 ms·
For me, the killer user case is having it as an AI assistant. A few months ago, I've started building a machine learning model for a keyboard iOS App as a solo
by mromanuk 3y ago
For me, the killer user case is having it as an AI assistant. A few months ago, I've started building a machine learning model for a keyboard iOS App as a solo dev, without python or deep learning knowledge.
The model I wanted to build, needed text correction, word completion and prediction in one pass. I'm pretty confident, it was an impossible task without the help of chatGPT, first GPT-3.5 and then GPT-4.
- bazmattaz 3y agoOh my I really hope that you are building the app of my dreams. I’m a an awful typer on my phone and on my desktop. Autocorrect is ok but I honestly don’t understand how we have all this amazing ML in the wild but we still seem to have the same shitty autocorrect. My dream autocorrect (powered by ML) learns how you type and how you speak. It learns what mistakes you always make (due to muscle memory) and corrects based on your past mistakes. Furthermore my dream autocorrect actually understands what you’re trying to say and corrects words based on the context of the conversation rather than how close the mistake you made is to some other word. For example, if someone texts me to say “I’m at the restaurant” and I type with a mistake “I’ll be right theyre” the autocorrect should understand the context of the conversation and rather than correct to “they’re” which is thinks is the correct spelling for this mistake, or autocorrects to “there” because it’s looking at the wider conversation. This is a poor example but I hope you get the point. I really don’t think what I’m asking for is hard. Apple should/could easily improve autocorrect
- mromanuk 3y agoI would love to build that keyboard, but unfortunately there is a RAM limit for keyboard apps. My current model is not so smart as I would like. For fun, I just tested your example, using only 8 tokens (current limitation): "restaurant I’ll be right theyre" and it's corrected to "restaurant I’ll be right there", there is hope :) I'm pretty sure that I can expand it a few more tokens without much impact in memory and latency.