Chatbot should be part of your ui instead of replacing the ui.

I made https://notionsmith.ai and technically it's "chat based", but the user isn't exposed to 99% of the chatting: the only chat interface on the site is there more as a bonus feature than anything.

On phones, I'd expect that voice will be a more popular input method than virtual keyboards.

I don’t know about you but freaking out all my fellow toileteers with loud phone conversations about my kinky exploits is one of the purest pleasures in life.

I regularly use speech-to-text transcription publicly. With my mouth close to the mic, I can speak softly enough that people outside of my personal space can't hear.

That being said, keyboards still have their place. Certainly, I use ChatGPT on my phone several times a week using keyboard input, and it's not particularly onerous.

There's no reason people couldn't make interfaces that use the same speaker as a phone call does.

I have a difficult time imagining myself trusting something as unpredictable as an LLM to perform any kind of "cleaning up" task on important data like my inbox. Perhaps future developments in utilizing language models in conjunction with less stochastic systems will make this an easier sell, but for now, I'm not seeing it.

The biggest UX work in the short term is going to be around giving people the right amount of transparency so they still feel in control. The actual LLM work is relatively easy and impressive.

You just ask them. I literally just prompted ChatGPT (3.5) to think about its answer again and explain what's wrong with it, and it did. Kept going 2 or 3 times, until it was sure it wasn't doing anything wrong, and magically the script it produced at that stage just worked.

Wanting to do some things by hand might be increasingly a thing only people over a certain age do.

What are some techniques that these products use apart from bounding context and prompt engineering? ReAct sounds like it might help: https://react-lm.github.io/

Suppose you configure your inbox such that you unpredictably don't see a small percentage of important emails. Suppose you miss an email from your boss telling you a very important client needs you to fix a critical bug today, and as a result you start working on that bug slightly later when your boss contacts you another way. Your boss might tell you to uninstall your LLM and just read all your email

By analogy it's socially more acceptable to have an outage because AWS is down than because insert_nich_provider is down even if insert_nich_provider has fewer outages. If insert_nich_provider has more outages it's even worse.

"Sorry I didn't see your important email; my AI assistant deleted it"

Do I really want to wave my arms to control an interface? No, they'd get tired immediately. A mouse on a desk where I can rest my arms isn't sexy because it's not new, but it's pretty much ideal.

They would, but only because you're not used to using them much.

Using our arms more would probably be really good for us.

If we had to use our legs and feet to move a mouse then computer programmers might be some of the fittest people on the planet, instead of some of the fattest.

I say this while lying on my bed and tapping with my fingers on my tablet... we're doomed...

Convert your command into the correct syntax.

Preview what the execution of the command looks like.

Review the changes after they occur.

Undo.

Just having it able to work a smart home or do basic things while talking natural is a big deal and a big increase in useful interface.

I really like my Alexa - I love the _idea_ of a conversation interface, except an Alexa isn’t that. It’s a call and response only. I’d love to be able to talk to a computer out loud conversationally that can take actions / give me info.

Even convos as simple as

‘Hey what’s the weather tomorrow’

‘Tomorrow will be 25c and raining’

‘What time will it rain?’

‘Not until 4pm’

This simple stuff is currently WAY outside the abilities of any ‘smart’ assistant.

Certainly with a weather API and the new ChatGPT API functions thing you can build that in a few days or less. Combine it with Whisper or Google voice input and Eleven Labs very realistic speech output.

I think there are quite a few groups with demos that can handle that particular weather thing and basics like it now.

Actually Google Assistant probably can handle follow ups to some degree.

There is very little that FFMPEG can't do as far as video manipulation, but getting a good CLI invocation is a lot of work, documentation surfing, and piecing things together from stackoverflow and Reddit. I don't really feel like committing such things to memory.

With ChatGPT, I can ask for it to make a parameterized bash script that takes a path for video input and output, and any other parameters of consequence and make a "converter from x format to Y using Z codec and nvidia hw accelerated encoding at W bit rate" and most of the time, the bash script that it gives me just works and I move it into my tool-bin.

It's nice! There are probably a lot of other tedious pieces of automation that it can handle well even in its early state.

That being said - it is far from perfect.

For example, I needed to use K6 to run a load test. It supports a million things, and it would have taken me a long while to figure out the right combo. With ChatGPT I had it running in 5 minutes.

Btw, I think Tim Cook should have released Vision with thought controls. Then it'd have been revolutionary....