But me clicking a button to see the details of my booking and getting transferred to a chat interface where my click was translated to a question with a "processing" progress bar irritated me to no end. And it replies with just a partial info inside a tiny chat bubble instead of having all the info in full screen! Just give me the freaking page with my booking details, godfuckingdamnit!
but as i was trying to explain, they missed the point and just created frustration for users
didn't want my article to sound like bullshit, that's why i built a poc to try and explain that it's not about having chatbots, but having entire components in a chronological order of the interactions with a website
in your case the booking details would be easily accessible just by scrolling up for instance
> web4ᵗʰ aka "the temporal web": user interactions across screen space and time of an immutable conversation
> What do we have?
> * The temporal web with conversation-first interfaces, leveraging decentralized communication protocols.
> * Forcing developers to really think at the isolated-component level, while reducing the surface of worry (remember mobile-first, constraints are a blessing).
> * Making their life simpler (even though they don't want it because… money, you know)
> * And most importantly making users' lives simpler: catering better for their intents and adding outstanding build-in support
That's a lot of bullshit bingo points...
Is it basically a chatbot as a UI?
To misuse his term, I thought "temporal web" was the recognition that the internet you're looking at now is different from yesterday's, because content get added, deleted and changed all the time. A web where you can rewind to "Version from $DATE" would be interesting...