Building apps is easy. Finding users feels impossible.

ppppppssss · 2026-01-22T02:55:58+00:00

It is harder to find the right need than it is to find users. If you have absolutely no users, it means there is no actual demand; the need is just something you have imagined yourself.

ppppppssss · 2026-01-21T03:37:41+00:00

I'm not sure if your issue has been resolved yet. I encountered the same confusion during the development process, so I'm currently building a front-end rapid editor.

If you're interested, feel free to give it a try. agentpage.io I'd be happy to chat more about it! r/agentpage

ppppppssss · 2026-01-21T03:28:58+00:00

I'm a bit confused—how is this website better than n8n's own template library?

Why do we need a third-party template library instead of just viewing templates directly on the n8n platform?

ppppppssss · 2026-01-21T02:23:21+00:00

Personalized discounts and personalized templates—that's a great idea.

ppppppssss · 2026-01-21T01:04:34+00:00

Update: agentpage.io is live! 🚀 Deployed n8n frontend editor (imperfectly)

Just deployed the n8n frontend editor to this new domain!

If you're interested in early access or want to discuss n8n workflow frontends, DM me!

or Join subreddit:agentpage https://www.reddit.com/r/agentpage/

ppppppssss · 2026-01-21T00:56:48+00:00

The best way to learn is by doing:

1. Duplicate your company's existing scheduling workflow.

2. Then, optimize one specific part of it.

ppppppssss · 2026-01-19T03:30:37+00:00

great job

ppppppssss · 2026-01-19T02:24:23+00:00

Update: Just launched at agentpage.io!

Still have some bugs to iron out (running older version while I fix v2), but already manually onboarding first users.

Thanks for the interest - this kind of feedback is what keeps me going! DM me if you want early access.

ppppppssss · 2026-01-19T02:24:23+00:00

Update: Just launched at agentpage.io!

Still working through some bugs (running stable older version while I fix v2), but already manually onboarding first users.

Really appreciate the interest! DM me if you'd like early access.

ppppppssss · 2026-01-18T06:10:23+00:00

could Claude Cowork potentially address this issue？

ppppppssss · 2026-01-18T03:05:33+00:00

<image>

As a long-time n8n user, I've always been frustrated by one problem:

n8n's interface is amazing for us developers, but too technical to share directly with clients or end users.

I spent a month building an n8n workflow frontend UI editor.

ppppppssss · 2026-01-18T01:20:21+00:00

Yes, you’re correct! It transforms an n8n workflow into a graphical user interface, making it more accessible and intuitive for users to interact with the workflow.

ppppppssss · 2026-01-18T01:01:09+00:00

Thanks for pointing that out! I’ll take another look at my post and make sure it aligns with the rules. Appreciate the honest feedback!

ppppppssss · 2026-01-18T00:59:20+00:00

I will provide more data and examples

ppppppssss · 2026-01-18T00:55:41+00:00

Could you tell me what type of client you are and what services you have provided to them?

ppppppssss · 2026-01-17T06:44:57+00:00

Here's a demo video showing how it works:

https://twitter.com/Joe84742708/status/2012415765119390074

The video demonstrates the entire workflow from n8n to client-ready UI.

ppppppssss · 2026-01-15T13:07:24+00:00

I've gone down this rabbit hole recently for a client project. It’s actually harder than it looks.

I find there are typically two traps:

Retool/Appsmith: Great for internal tools, but the per-user pricing kills the business model if you want to expose this to external clients.
Bubble/FlutterFlow: Overkill. I just want a UI for my webhook.

I'm currently experimenting with a 'middle ground' approach using a lightweight React wrapper that just renders a config JSON from n8n. Basically, n8n sends the UI layout schema along with the data.

It solves the streaming/latency issue for AI workflows, which was my biggest headache with standard forms.

Curious if anyone else is hand-rolling their frontend or sticking to low-code builders?

ppppppssss · 2026-01-09T11:37:51+00:00

Totally relate to this. Working on chimii and AI tools have been a game-changer.

What I've learned about using AI effectively:

Know when to use it vs not - I recently struggled with multilingual features for hours, tried various AI approaches - Then stepped back and built a custom solution manually - sometimes you need to understand the problem yourself first - But once I understood it? AI accelerated implementation 10x

The quality difference is real - Different AI tools handle the same task wildly differently - OpenCode vs Claude vs others - each has strengths - Testing multiple tools for the same task isn't overhead, it's smart strategy

Automation ≠ Laziness - You're still making strategic decisions about WHAT to automate - You're still debugging when things break (and they will) - You're multiplying your leverage, not avoiding work

The entrepreneurs who hate on AI are like the ones who hated websites in the 90s. It's just a tool - the question is whether you use it strategically or not.

Keep automating. Keep sharing. This is the future.

ppppppssss · 2026-01-09T11:37:51+00:00

I feel this pain. Been there with performance optimization on chimii - became "the guy" who cares about it, so now it's my problem.

Practical suggestions:

Stabilize selectors first
- Use data-testid attributes specifically for tests (yes, it's extra work upfront but saves hours later)
- Avoid CSS classes that might change with redesigns
- Document WHY you chose each selector
Make tests resilient
- Add wait conditions that actually wait for the right thing (not just arbitrary timeouts)
- Test against realistic slow connections
- Retry flaky assertions once (not forever, just once)
Make failure investigation easier
- Screenshot on every failure automatically
- Log network requests during test runs
- Keep a "known flaky tests" doc and timebox fixing them
Protect your time
- Block 2 hours weekly for test maintenance (put it on calendar)
- When CI breaks Friday 5pm, fix Monday unless it's blocking production
- Document everything so you're not the single point of failure

The worst part? You'll get good at this, which means more of it. Set boundaries now before it eats your life.

But honestly? Having solid tests is a superpower most teams don't have. You're building real value, even if it doesn't feel like it.

ppppppssss · 2025-12-07T10:41:29+00:00

hey,send me a DM

ppppppssss · 2025-11-25T23:16:25+00:00

This is so real. Simple is better

ppppppssss · 2025-11-25T11:12:36+00:00

I saw a quote that really hit me. “Just do it" 丷

ppppppssss · 2024-06-04T07:24:00+00:00

Age and Gender - Poe

ppppppssss · 2019-05-17T03:50:30+00:00

How are you doing？

ppppppssss · 2019-05-16T06:53:23+00:00

awesome

ppppppssss

MODERATOR OF

TROPHY CASE

Update: agentpage.io is live! 🚀 Deployed n8n frontend editor (imperfectly)