Bilgi Karan

UX, Innovation, Strategy, and Inclusive Design. Views my own.

[Bilgi Karan @machineError]

UX Strategy sounds mystical until you understand this simple fact... No stakeholder wants to hear about yet another strategy. And I'm yet to hear a top manager ask for a UX Strategy.
https://t.co/EMHP6raYH1

[Bilgi Karan @machineError]

The question is who are the thousands of accounts liking this post. Are they current users of Arc who hated it? Or hardline fans of Dia who don’t want Arc as a competitor? Confused. 🤔

I’ll miss Arc dearly.

[Arc @arcinternet]

We've decided to sunset Arc on December 22, 2026.

That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community.

Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward.

We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how:

· Your passwords, bookmarks, extensions and history come over to Dia seamlessly.
· Spaces, Folders, and Tab Groups are in Dia and import over with your data intact.
· Dia now surpasses Arc benchmarks in stability, speed, and security.
· The browser features you use in Arc are free in Dia, and the AI is optional.

Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.

[Bilgi Karan @machineError]

@KaAnDK Orimer?

[Bilgi Karan @machineError]

Wow. I rarely see so many different views and so few likes on each reply in a post. Does this simply say that it is a yet-to-be-solved problem?

[Tanay Mehta @serious_mehta]

Every time I start a new session, my agent has to re-learn what everything in my project it from scratch. This is such a repetitive waste of tokens. AGENTS [dot] md doesn't solve this either because it's hard to keep it up to date and still burns tokens.

Any proper solutions?

[Bilgi Karan @machineError]

@brad_frost @argyleink Someone should start a subreddit with that name! /ihadnoideathatwasthenameofthatthing

[Bilgi Karan @machineError]

@CharlesPattson Applauding you for the tasteful launch! It is a pleasure to use.

[Bilgi Karan @machineError]

@KaAnDK Awesome! Recognize your achievement here not only as a very cool demo but also a mental floss for many designers who are trying to find the next paradigm beyond sidebar chat.

[Bilgi Karan @machineError]

Until now, we have been filming a theater play. This is like the moment when a camera operator stopped and repositioned the camera for the first time.

[Jason Fried @jasonfried]

For years, maybe a decade, I've wanted to build a writing tool that just did a few things I couldn't find anywhere else.

A system that mimicked how I think when I write. A system that provided clear affordances, features, and places to do the things I wanted to do. A way to play with my writing as I'm writing it. A way to settle into just the right way to say something.

It never made sense to make it a 37signals product because it's not commercially viable, nor would it be worth pulling people off their other work to hack on this. Plus, it would have taken months the old way.

So this weekend I just made it myself, with Claude's help.

It's called Write_On and the short video walks you through it.

Essentially it's "alternative control" at the word, sentence, and paragraph level, plus a way to dim stuff back, and stash stuff near by. Not version control, but alternative control. You'll see what I mean when you watch the video below.

So here it is. Write_On.

[Bilgi Karan @machineError]

@Aweiland A metric ton of pixels in Europe is a megapixel whereas in US it is 2067.32 thousand pixels.

[Bilgi Karan @machineError]

@brad_frost @LiaskasV Impressed!

[Bilgi Karan @machineError]

Yes, you can use the Jev API but can you write a decent user story?

https://t.co/jssislD3E1

[Bilgi Karan @machineError]

@brad_frost Happy learning! Get ready for a slightly steep learning curve but surprising superpowers on the other side of the curve.

[Bilgi Karan @machineError]

@hobdaydesign Yes! 🙌

https://t.co/ZeM7GvtjrT

[Bilgi Karan @machineError]

11/ Find Meaningful Solutions - When an escalator fails, it is still a set of stairs. How does your product behave when internet fails?

[Bilgi Karan @machineError]

With future generations of Jev I hope we will once and for all get rid of the CAPTCHA torture. @typesafeai

[Bilgi Karan @machineError]

@darylginn Do it. ;)

https://t.co/DPA4UIxWZj

[Bilgi Karan @machineError]

@aydaoz Strongly agree!

[Bilgi Karan @machineError]

“When ChatGPT shipped, we were all blown away by…ChatGPT. When Jev shipped, we were all blown away by what everyone was making with it.”

These two sentences summarize what I mean when I say Careful Innovation.

[Justin Schroeder @jpschroeder]

I’ve put a ton of tokens through Jev now, and...I have thoughts.

1. The big labs lost the script

TypeSafe’s intro video says, “We’re building prod, not God” — and can I just say? Hell yeah. @typesafeai built something for engineers like me, so I can build products for people like your mom (she says hi btw). They’re not trying to create “Machines of Loving Grace”; they’re trying to build things that let OTHER HUMAN BEINGS create new types of products.

The proof is in the pudding. When ChatGPT shipped, we were all blown away by…ChatGPT. When Jev shipped, we were all blown away by what everyone was making with it.

I cannot tell you how refreshing this is. It takes a sincere form of humility to believe that you, the creator of a technology, will not be the best at deploying the technology into the marketplace. The big labs, especially Anthropic, have proven not to have this humility…and now everyone hates AI. Thanks, Dario.

I guess what I’m saying is: Diogo for president.

2. Ultra-smart classifiers were genuinely a missing primitive.

I don’t know how this got missed. Diogo calls it “machine-native intelligence,” and that’s really what it is. I cannot tell you how much bending and twisting I've had to do with LLMs to get them to act like a classifier when they just weren’t. I’m absolutely shocked this is the first time this “type” of model has come to market.

These models will unlock AI utility for entire industries: robotics, trucking, aviation, meteorology, finance, defense, retail…even your smart coffee mug is going to use this.

3. It’s still too expensive

Jev is really, really cheap compared to LLMs. But you don’t use it like an LLM. In my full self-driving example, or any robotics example, you’ll be making decisions several times per second continuously. The #1 value proposition of a model like this is speed and cost.

To be clear, at current pricing, the model will still be successful and well integrated. It will be able to replace a number of tasks that were already being performed (poorly) by LLMs. However, to unlock industrial-scale demand (Jevons paradox), I believe it needs to be roughly 10x cheaper.

Currently, Jev is $0.042/M input, which is actually 7x more expensive than a cache read on DeepSeek V4.1 Flash ($0.006). If our industrial application requires decisions at 10 Hz and we provide only 10k of context, that would cost $0.0042/second to operate, or $15/hour, $600/week, etc.

The good news is Diogo said on a recent AMA that they have substantial margin at their current pricing and have already considered dropping the cost further. I hope it's a lot further.

4. Latency is a real limiter

I really hope TypeSafe AI works with an edge network provider to improve the co-location of models and reduce network latency. Ultimately, these models really need to run on-device. I would even be willing to pay some kind of recurring license fee to have a great closed model running on my own hardware, just so I can reduce the TTD (Time To Decision) as much as possible. Imagine running a model like this at 60 Hz, or even 120 Hz.

At that point, we’re looking at a new kind of logic gate — we can’t even imagine what that will be like.

In summary, this one really is a game changer for everyone building AI products, and, assuming cost and latency are further improved…it’ll be a game changer for everyone doing anything.

[Bilgi Karan @machineError]

In less than an hour, I’ll be on stage @WaysConf talking about how to innovate carefully. Let me know if you want to see a post about it. Thanks for the nice wishes in the morning @brad_frost !

[Bilgi Karan @machineError]

@antonsten @kevintwohy @_moneill_ Just call it Agentic Dining. 😁

[Bilgi Karan @machineError]

@steveruizok So cool when two people I respect also respect each other. You are both the rocks of software design of this era.

[Bilgi Karan @machineError]

@semihdotcom Check your DM. Thanks 🙏!