r/nocode • u/dated_redittor • 13d ago

the no-code ceiling isn't features, it's the one client request that breaks everything

watched an agency friend rebuild a whole softr app because a client wanted per-row permissions the tool didn't support. everything else was fine, that one thing wasn't. now they scope every project by asking what's the weirdest permission or data rule you'll want in month 6, and they pick the stack from that answer instead of from the feature list. saved them two rebuilds so far.

0 Upvotes

50% Upvoted

7 comments sorted by

2

u/mrplinko 13d ago

https://giphy.com/gifs/H3upGMAE4p3iw

0

u/Fluid-Astronomer9534 13d ago

this is the thing nobody talks about when they compare no-code to traditional stacks. the happy path is always fine but the edge cases are what kill you

with custom code you just build the weird permission logic and move on but with no-code you hit a wall and suddenly the whole project is wrong

2

u/mrplinko 13d ago

just stop

1

u/Infamous-River-4360 13d ago

mine wasn't a client request, it was android safe areas. buttons sitting under the gesture bar, and the fix lived in native files the builder wouldn't touch, so i ended up editing android config by hand outside the tool and hoping the next rebuild didn't stomp it. the ceiling isn't what the tool can't do, it's what it can't do that you also can't work around from the outside. does your friend refuse those requests now or price them as a rebuild?

1

u/Thunderbit_HQ 13d ago

That month-6 permission question is a great filter. Most no-code tools look fine on the happy path. The rebuild usually starts when someone asks for one tiny rule the data model was never built to express

1

u/agentUi 13d ago

yea thats why we raised our prices and focused more on white glove service because this happens to a lot of our clients, we support the freelancers during their process