Splatin

building a TODO \ AI assistant app

[Splatin @Splatinn]

Changed sub from codex to claude..

After trying it for 3 days

Im so fucked.

@thsottiaux will never leave you again boss 🙏

[Splatin @Splatinn]

Build 234 looking good

[Splatin @Splatinn]

Build 185 looking good

[Splatin @Splatinn]

ive tested the top 10 frontend design skills on Sol 5.6

UX UI Pro was the absolute worse by far 🤔

[Splatin @Splatinn]

Touching grass till SOL release tomorrow 🍃🌤️

[Splatin @Splatinn]

big refractor loading

[Splatin @Splatinn]

Too little AI apps care about privacy and encryption

[Splatin @Splatinn]

oh boy lot's of engegment farming on founders\vibe coding X 🤣🤣

[Splatin @Splatinn]

Final new task edit version 🙆‍♂️

- minimalist UI
- bigger elements while taking less space overall
- more “human” controls

+ you can officially Delegate(!) tasks to your agent via the Nala MCP ✅

Just tested with 9 tasks in one go and after 30 minutes all was done 👍

[Splatin @Splatinn]

While 0 edit options removed

Love minimalism

[Splatin @Splatinn]

Rate my design? 😁

Build 189 - Task edit before and after

Imo 2 > 6

[Splatin @Splatinn]

Rate my design? 😁

Build 189 - Task edit before and after

Imo 2 > 6

[Splatin @Splatinn]

Build 185 looking good

[Splatin @Splatinn]

About 20-30 hrs of work for that only btw

Aiming for the 10/10 ux

[Splatin @Splatinn]

People might not realize this:

AI chat UI is WAY MORE COMPLEX than it looks.

In a normal chat, the newest message naturally sits at the bottom.

But in an AI chat, after you send a message, that message often needs to become the new anchor of the screen, near the top, so the AI response can stream underneath it.

That sounds simple, but it creates a lot of hidden complexity:

You still keep the messages in chronological order.

But the scroll behavior changes depending on context:
- if the user is reading history, don’t yank them back down
- if a new message was just sent, pin that turn near the top
- if the AI is streaming, keep the response visible below it
- if the keyboard opens or the input grows, preserve the exact visual position
- if there isn’t enough content under the latest message, create enough invisible space so the anchor can still work

So the hard part isn’t rendering bubbles.

The hard part is making the conversation feel stable while the content, keyboard, composer height, and streaming response are all changing at the same time.

Great chat UX is mostly invisible scroll math.

[Splatin @Splatinn]

Starting to hunt bugs after the swift migration, overall not too bad…

Liquid glass is beautiful

[Splatin @Splatinn]

Fuck paywalls

[Splatin @Splatinn]

thinking about the free tier for Nala like this:

if one good message can help organize your whole week, a few dozen messages is actually enough to feel whether the product is useful

[Splatin @Splatinn]

thinking about the free tier for Nala like this:

if one good message can help organize your whole week, a few dozen messages is actually enough to feel whether the product is useful

[Splatin @Splatinn]

Today’s glamorous startup work:\n\nchat bugs, keyboard behavior, release stability, agent handoff weirdness.\n\nThe stuff nobody screenshots but everyone feels.

[Splatin @Splatinn]

building an AI assistant is mostly discovering how many tiny things humans do automatically and then realizing the product has to learn those too

[Splatin @Splatinn]

I’m building Nala to manage AI agents, not just talk to them

assign Codex / Claude a task
give them context
send them to work
let Nala handle the follow-up mess

agent babysitting is not the future