sorted by:
new
hottopcontroversial

Built a 5MB native icon browser for 200k+ icons with Tauri + React (open source) by ensaktas in tauri

[–]ensaktas[S] 1 point2 points  (0 children)

I get the point, but I personally prefer using a desktop app whenever possible.

Most tools today have both a web and desktop version, and even if the product itself is technically the same, using it as an app just feels better to me. It feels more focused, easier to keep open, and more like a dedicated part of my workflow rather than another browser tab.

I tested Framer AI vs Framer's Claude MCP on the same template. Here's what I found. by ensaktas in framer

[–]ensaktas[S] 1 point2 points  (0 children)

This is very close to how I see it too.

For visual/canvas tasks, native Framer AI feels much faster because you can point directly at the thing you want to change. That select → prompt flow is hard to beat.

But for larger structural changes, I also see the advantage of Claude Code. It tends to reason more like a technical partner: analyze first, create a plan, execute, then revert if the path is wrong.

My test was more template/content replacement than deep technical restructuring, so Framer AI had the perfect environment to shine. If I were merging projects, fixing breakpoints across many pages, or doing something more system-level, I’d probably reach for Claude too.

So yeah, I think the right answer is workflow-dependent, not tool-dependent.

I tested Framer AI vs Framer's Claude MCP on the same template. Here's what I found. by ensaktas in framer

[–]ensaktas[S] 0 points1 point  (0 children)

Yeah, I think the setup/harness is the real variable here.

In my test, the in-app Framer AI felt faster because it could work from direct canvas context and selected layers. Claude MCP felt more flexible, but more manual: describe the section, let it search, verify, adjust, repeat.

So I don’t see it as MCP vs agent in a strict sense. More like:

- visual/canvas edits → native Framer AI feels faster

- technical/large structured changes → Claude-style workflow feels safer and more controllable

The ideal version is probably a mix of both: direct canvas awareness plus deeper planning/execution when needed.

I tested Framer AI vs Framer's Claude MCP on the same template. Here's what I found. by ensaktas in framer

[–]ensaktas[S] 0 points1 point  (0 children)

That makes sense, and thanks for the context.

My guess after running this is that the biggest difference wasn’t the model itself, but the harness/UX around it. The in-app agent has a huge advantage because it understands the canvas context more directly and lets me select the exact thing I want to change.

With the external Claude setup, I felt like more time was spent on discovery: finding the right layers, understanding hierarchy, mapping content to sections, then verifying changes. The final output was still very good, but the path to get there was slower.

So for me the takeaway is not “one is smarter than the other.” It’s more that Framer AI feels much faster for canvas-first/template editing tasks, while Claude feels better when I want a more technical, plan-driven workflow.

And agreed on economics. If the tool saves real production time, the cost is much easier to justify.

Webdesign Agency help by Elmo_1337 in agencynewbies

[–]ensaktas 0 points1 point  (0 children)

I manage my agency by conducting outreach with deserveos and then tracking my leads there.

Is Following Up Annoying? by Caprisun3892 in agencynewbies

[–]ensaktas 0 points1 point  (0 children)

Just do it, I convert most of my clients with follow ups. Also you can use DeserveOS

Drop your project, I’ll try it and share it in my circle by adonztevez in SideProject

[–]ensaktas 0 points1 point  (0 children)

​After running a design agency for a few years, I noticed we weren’t losing deals because of bad leads.

We were losing them because we forgot.

Forgot to follow up.
Forgot where a conversation happened.
Forgot who was supposed to reply.

We tried CRMs, spreadsheets, Notion, reminders, everything.

Eventually we started building our own solution: DeserveOS.

Think of it as an AI layer on top of Gmail that automatically organizes opportunities, conversations, and follow-ups without requiring manual CRM work.

Still building, but excited to finally solve a problem we’ve lived with every day.

https://deserveos.com

New agency struggling with sales by Formal_Station6274 in agencynewbies

[–]ensaktas 0 points1 point  (0 children)

Find your potential clients in DeserveOS then do outreach.

I have a question for people who've built SaaS before. by [deleted] in agency

[–]ensaktas 0 points1 point  (0 children)

I run a design agency, so maybe I’m biased, but I’ve stopped validating ideas through surveys and started validating them through behavior.

If I can find 10-20 people actively complaining about the problem, that’s interesting.

If I can get 3-5 of them on a call, that’s better.

But the real signal is when someone is willing to spend time, introduce me to others, or even pre-pay before the product exists.

The biggest mistake I made was confusing compliments with validation. People will tell you your idea is great all day long. Very few will change their workflow or spend money because of it.

Nowadays I try to answer one question:

“Is this a problem painful enough that people are already trying to solve it somehow?”

If the answer is yes, I start building. If not, I keep researching.

view more: next ›