惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The Cloudflare Blog
U
Unit 42
F
Fortinet All Blogs
雷峰网
雷峰网
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
月光博客
月光博客
Y
Y Combinator Blog
罗磊的独立博客
V
Visual Studio Blog
大猫的无限游戏
大猫的无限游戏
J
Java Code Geeks
量子位
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
爱范儿
爱范儿
B
Blog RSS Feed
aimingoo的专栏
aimingoo的专栏
有赞技术团队
有赞技术团队
T
Tailwind CSS Blog
Microsoft Security Blog
Microsoft Security Blog
L
LangChain Blog
I
InfoQ
博客园 - 叶小钗
博客园 - 聂微东
Last Week in AI
Last Week in AI

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I tried to make AI conversations feel less like input/out...
Robert Adria · 2026-05-10 · via DEV Community

Over the past year, I’ve been using a lot of AI tools. At first, they felt impressive—fast, capable, almost magical in how quickly they could respond. But over time, something started to feel off. The more I used them, the more every interaction began to feel the same. Predictable. Structured. Transactional.

Most conversations followed a simple loop: you type something, you get a response, and then you move on. Even when systems try to feel conversational, they’re still built around that same pattern—input, output, done. There’s no real sense of continuity, no presence, nothing that feels like an actual interaction unfolding over time.

What made this more uncomfortable was realizing how these systems handle conversations behind the scenes. Something that feels personal often isn’t treated that way. Conversations are stored, analyzed, sometimes reused. Once you become aware of that, it subtly changes how you engage. You hesitate more. You filter more. The interaction becomes less natural.

I thought avatars might change that. Adding a face, a voice, a sense of presence—on paper, it sounds like the missing piece. But in practice, it introduced a different kind of friction. Many of these systems are metered, charging per minute or per interaction. That changes behavior immediately. Instead of speaking freely, you start optimizing. You become aware of time, cost, efficiency. And that awareness breaks the illusion completely.

At some point, I stopped thinking about features and started thinking about the experience itself. Not how to make AI more powerful, but how to make it feel different. What would happen if conversations weren’t stored at all? If interaction wasn’t limited or measured? If the goal wasn’t just to generate responses, but to create something that felt more like a real exchange?

That question led me to start building something of my own. Not as a finished product, but as an experiment. The idea was simple in theory: remove as much friction as possible and see how people behave. In practice, it turned out to be much harder than expected. Most systems are built around persistence, tracking, and optimization. Removing those assumptions forces you to rethink how everything works—from session handling to how continuity is maintained without storing history.

Another challenge was realizing how vague the idea of “more human” actually is. It’s easy to say, but difficult to implement. It doesn’t come from one feature or one breakthrough. It comes from small details—timing, tone, how responses flow, how natural the interaction feels over time. These are subtle things, but they shape the entire experience.

One of the most interesting things I noticed during this process was how behavior changes when constraints are removed. When people feel like they’re not being tracked and not being limited, they interact differently. More openly. More casually. Less like they’re issuing commands, and more like they’re actually engaging in something.

This experiment eventually became what I’m building now, but the product itself feels secondary to the question behind it. Should AI remain a tool—efficient, structured, predictable? Or is there space for something that feels closer to an interaction, even if it’s imperfect?

User Interface built in pure HTML, CSS and JS

I don’t think there’s a single correct answer yet. I’m still figuring it out as I go. But it’s been interesting to explore what happens when you shift the focus away from output and toward experience.

I’d be genuinely curious to hear how others think about this. When you use AI, do you want it to stay as a tool, or do you find yourself wanting something that feels more like a conversation?