If I need, say, authentication, why do I need to install a library and then read a bunch of documentation on how to use it? Why can't I simply plug it in (just like low-code!) and have it automatically work?
I think there is a lot of room to improve developer tooling and that the effort spent there would produce much greater rewards than developing a higher level abstraction, such as a pluggable authentication widget aimed at non-programmers.
Alternatively, tell me your complicated auth flows that will not have users running away screaming and are, therefor, bad ideas and should be replaced by cookie cutter stuff. Because that is where all of these things end up.
Drop in the plugin you want, configure the API keys, and then wire it into your User model. Then you can customize the urls, views, and emails.
You still have to read a fair amount of documentation and a lot of developers don't like the extra up-front work and reinvent the wheel because it's "simpler".
The simple use cases should just be plug and play. If you want a different solution: here are the tools, here is the documentation, have fun.
However, we're definitely not aiming it at non-programmers. I don't think completely general low/no-code solutions will ever take off. Everyone wants things far too custom, and at some point you won’t be able to beat the programming language of the time. Companies like retool are doing a great job in specific verticals — and I think it will always stay that way.
I think the next generation of dev-tools are going to be pretty impressive, especially with how easy and modular React components are — I’m bullish that React will become “low-code”
I'm over-simplifying of course, but these things sound simple until you ask all the "but-then" and "what-if". If someone actually makes them simple in a way that still lets me cover those cases I'll be the first to stop writing authN/authZ code.
AWS very much decoupled authentication from authorization with Cognito and it works very well.
The model is not perfect and does not work well for every type of process, but we have a few very satisfied customers. Just enough success to slowly grow our business and buy us enough free time to build and improve Lowdefy.
Currently it's working really well, like one gear turns the next. The apps we sell help us test and improve our low-code platform. The more apps we sell the more we invest in our platform and as a result all our apps get better, more feature rich and easier to maintain. Hopefully next, by building an open-source community around Lowdefy we can accelerate this cycle.
A visual editor is definitely on our roadmap. Our strategy is to make the schema easy to read, write and understand. We want to ensure the dev experience of working with the Lowdefy schema is first class so that change review and version control can be as productive as possible.
Adding a visual dev interface is resource intensive can easily distort the schema quality. We figured by first maturing the schema and making sure it works well with dev tooling, we can add a visual dev interface on top as Lowdefy becomes more popular.
I'm founder of a startup that develops DevOps tooling and we're debating how early to build out the ui. (We have the basics down with Vue like I mentioned.)
So then we really asked how lean can we make this platform to keep it agile while experimenting with the mechanics of the schema. After more than a year of that the experimentation paid off and we now have a very flexible, yet understandable schema for building apps.
But yes. Adding a visual editor on top is one of our goals - and we are getting closer and closer to making it happen.
To be fair, we did start adding custom code after the first few years, but we went a really long way before losing the last of the low-code platform.
One is a Cameo-like platform for LatAm, the other is a TikTok like short-form audio app .
I've been incredibly impressed by the platform and extensibility. If you have basic coding skills I think it's much more powerful than Webflow or other platforms.
Are you allowed to share links to their businesses?
That being said there are many people who have built businesses around helping companies with setting up WordPress and Shopify sites, which are all about navigating their admin panel, dashboards, etc. You would not be the first person to help set up websites with no code.
You can read more about how it was built here:.
https://www.foxy.io/blog/how-okiefoodtrucks-is-using-foxy-we...
It's always going to be a money and time pit when you need to outsource to fix any problems.
If you don't know code, hire someone on your team who does. :)
Yeah, but that would be a pretty crappy low-code platform if when things went wrong, they did not handle it, and instead told their customers to go hire coders.
"No code" doesn't mean you don't have to implement things yourself. You are simply limited to the platform's baked in abstractions in exchange for "not having to write code".
Your services may eventually not map well to the capabilities of the platform, and it may cause problems. In such cases, the easiest and likely best solution is to offload functionality to a private server running custom code that interacts with the interfaces to the existing platform.
The whole "no code" thing is spun as "empowering entrepreneurs", but there is a philosophy underlying it that implementation details don't matter, and programmers aren't needed. It may be true for some businesses who are in non-technical sectors, but if you are selling digital services themselves "no code" will only take you so far.
Starting a tech business on a low code environment is a great idea. In fact, is probably the best idea since it means iterating fast, easy to identify functional requirements and gets you to market fit ASAP without breaking the bank.
Running a tech business at scale on a low code environment is a whole another topic (the OP explicitly mentioned "built").
TL;DR - Unless you're building hard tech (AI platforms, VR, etc.), then low code environments are great ways to build businesses.
I'll wait
advised
Thanks for the snark though.
Eeeehhhh - it depends on where and how your business delivers value. As others have said, the problem with low-code platforms is they're generally proprietary, which means it's much harder to wean yourself off once you get started - though that's not my main concern: my main concern is that low-code platforms necessarily mean ceding control over your product's E2E: if you accept that for the productivity gains from not having to get bogged-down in the details, sure - but for a lot of stuff it's a very limiting factor.
My current company's focus is a small suite of domain-specific line-of-business SaaS apps - nothing special there. It does mean that our entrenched and incumbent competitors built "unsexy" ASP.NET WebForms (ew) pages over a decade ago and haven't maintained them - or they're relatively modern but built on-top of heavy SPA frameworks that ultimately detract rather than benefit the E2E UX (an egregious example is a competitor that has a traditional SSR web-app, except they load Angular2+ in every single page-load... it's stuff like that which makes users develop negative sentiment around a web-application.
Another anecdote is a simple reporting system built-in to one of our products: again, it's nothing special: just a data warehouse in Azure with some clever hand-written SQL queries to populate some simple HTML tables with ChartJS thrown-in for good measure - and one of our biggest customers' buyers was completely floored by our demo - I thought he was being sarcastic or facetious in the meeting but it turned out that they were using another of our competitors who built their similar reporting functionality using a low-code-ish platform where the web-service is a dumb store of data and the client JS code has to retrieve and process all the data itself... (with no multi-tenant access-controls either) so it took 30+ seconds (and thousands of AJAX requests) for their report to load.
...now you can argue that my anecdotes concern companies that either let their product go stale or had an incompetent (or under-funded and over-worked) development team - but that doesn't detract from my point that low-code tools and platforms make it very difficult, if not impossible, to root-out E2E issues. Having an app with poor performance is bad enough, but having an app where the low-code platform you built-on makes it impossible to address some core user-experience fault is why I have a hard line against low-code in principle. Another example of this is this one particular low-code web-app platform (no names please) which hard-codes in some old version of jQuery which then precludes bringing in other client-side libraries or third-party widgets (think: stuff like ZenDesk chat support, and their widget's bad enough already).
So yes, it's cliche: but "it's a tradeoff" - but just be mindful of exactly what you're trading-away in exchange for developer productivity. You're either the kind of company that looks at, say, Blackboard and either sees them as a success for their large user-base - or you're someone who actually used it and consequently will carry that bad-taste-in-the-mouth over to not recommend purchasing it if they're ever put a position where they make decisions about what software/systems an org buys. My opinion is that the user-experience matters, and low-code tools make it easy to ruin the E2E UX if you're not careful.
And I can't believe this needs to be said, but yes it can be smart to hire programmers to build 5% of your system instead of 100%.
> Trying to be an entrepreneur in an area that you don't have experience in is a money pit.
Y Combinator exists as an explicit bet against this proposition. (They publicly said they wanted to find the youngest age where entrepreneurs could be successful.) To take another, AirBnB is a good counter-example. Should the founders have been experts in programming? Data science? Recommendations engines? Hospitality? If you erect enough artificial barriers, nobody will launch anything.
It was extraordinarily fast for static content, although forms and controls were a bit more difficult. We ended up building out some primitives using Stimulus and ActionView Components to make life easier, and overall it was a surprisingly nice workflow.
Would I recommend it to others? Possibly. It worked really well for our situation where time and agility were valued above all else, but I attribute the success there in part to the way the team worked and the fact that our founder was so proficient with it.
MSS, DCAPP, SYSLOG (in Portuguese) https://www.sysdevmss.com/ https://sysdevdcapp.com/ https://www.syslogmobile.com/ MSS has more than 15 years on the market. So it's a lot of people relying their sales on a software that was build with a RAD tool.
Our costumers are manly 3 types: Consulting companies that resell MSS/DCAPP or use Kalipso to create their own solution. Freelancers that use Kalipso to create their own solutions and bespoke programs to costumers. And big companies with an IT department that use Kalipso internally. MSS/DCAPP is manly for Portuguese/Spanish language countries. Kalipso is used everywhere from Argentina to Vietnam. And we ha no idea how many apps are out there build because we don't have royalties and we don't collect any data.
I’m trying to be less judgey generally, but there were a few things in the one video I started to watch that had me giving some wild side-eye so I stopped watching and never went back.
There are a lot of consulting services exclusively focused on building for Outsystems, Mendix, Webflow, Bubble, Zapier, Wix.com, IBM Apex, Appsheet, and Shopify platforms.
The number of entrepreneurs building on low code/no code platforms probably runs into hundred of thousands. Maybe even more if you count the consulting businesses built for the Salesforce Lightning platform.
I run an open source low code platform to build internal apps called Appsmith[0]. We know dozens of consulting companies who've built Appsmith apps for their clients. I bet every fast growing low code/no code product has small businesses built on it because the tech consulting market is just so huge.
Everything starts as low code, but complexity always creeps in. It's like Factorio, the code will grow.
For myself, I just built a website with UMSO, newsletter with GetRevue, and public knowledge base with Notion and Super.so
My newsletter: https://www.getrevue.co/profile/alfiemarsh My website: www.alfie-marsh.com
Public knowledge base: i actually stopped using Super.so because it didn't show databases well - product still has some work to do
I'm also looking into Circle for a membership community and Bubble to create apps.
At some point the low-code became more-code than our usual spring boot/rails approach. Integrations with libraries that the platform does not contain functionality for is a major headache.
I think a sweet spot would be a low-code/no-code platform with minimal abstraction built on top of currently popular web frameworks.
RPA: robotframework - along with python+java
Also upgrades need to be carefully planned when using low-code tools as we have seen more breaking changes when compared to popular opensource frameworks.
And if you want to go back 20 years, here’s a link of sites built with Microsoft Frontpage :)
https://trends.builtwith.com/websitelist/Microsoft-Frontpage
PS: I don’t work there anymore as I am now building a No-code SaaS company called Heyflow.app right now.
Now that I have your attention, let me tell you that critics of no-code and low code think about it wrong. It is not a silver bullet for the whole product. Think of your product as modules/micro services not as a monolith (VPs of Engineering reading this and saying Duh!). Some modules can use No-code, some low code, some NodeJS scripting depending on the use case and keeping them all loosely coupled allows to make future changes easily. No-code is another tool in Batman’s belt, not the whole belt.
What are you working on now?
https://docs.google.com/spreadsheets/d/1tBrZEMFK9XNWxiqOxE8o...
Been contemplating whether to leverage no-code tools to help level-up the functionality and visualizations
Would appreciate any pointers as appropriate. Thanks.
You should also include a general net worth, daily net gain, weekly net gain on 7 day lag, and monthly/quarterly to see how you're really doing. Just the number and a basic chart can do so much more to clear it up.
Etsy and BTC, congrats, same here too.
What I did was create a general dashboard, of my daily net worth and also gone as far as see my daily spend - I setup email alerts on my credit card, withdrawls and used O365 flow to capture the number and append it to a spreadsheet which then is pushed to the dashboard on a hourly cadence.
Bank accounts value Stocks Crypto Housing equity (this one is static, just took value and apply a custom appreciation rate, low, but figue if 3% annual is correct, just divide by 12, and do it monthly) Gross Revenue/Paycheck income. Daily Spend Daily spend average.
But I admit it is different from just tracking investments, hopefully this post makes sense, I feel like I went off quite a bit.
I'll look into powerbi - thanks for the suggestion.
It sounds like you're using it to track your budget & net worth.
I actually disagree with tracking my investments this granularly. Just because we can, doesn't mean we should. I find it's better to zoom out when it comes to investing and let time & compounding work for me. If it was granular to the day, I think I'd drive myself crazy! :)
Lots of opportunity with these tools and platforms!
Any domain examples you can share where it's been successful?
Without building in this way there is no way they would be growing at the rate they are - they would still be writing their MVP (they are now valued at >$100m in year 3, and are still supported entirely by spreadsheets as the investment in terms of focus is towards anything customer facing - they know they need to sort everything else out, it’s just everything has to be prioritised). Also their ops are still evolving so quickly that any investment in writing code to support ops is likely to slow down ops change (who need to be able to respond to issues nobody has seen before).
What's important for me is that users can ramp up from drag 'n drop to coding by hand. Otherwise they might just end up feeling stuck with the tool.
I'd rather see users use and then discard our tool once they ramped up their skills, in favour of then just writing code using our tech. Much better than getting stuck forever in our competitors' rather limited toy editors. :)
I built the Castup[1] website using Webflow, use Outgrow for onboarding, Stripe for payments, Slack for communication. It’s a productized service startup in the podcasting space but I have enough knowledge of no-code tools to build a SaaS as well.
I was full-time on it with a small team for 18 months when we were acquired by Zapier in March this year.
Our revenue was public in 2019/2020-ish and pulled in around $420k/year
Woocommerce + a POD plugin/partner + Trello
*all designs are hand custom-made however until we launch our Ai powered version.
Unity is not entirely no-code, but it comes incredibly close. I'm willing to bet there are a handful of iOS/Android games out there with barely a line or two of custom code written.
You essentially have one sub-processor (the platform). The well-funded no code platforms have established DPAs that make compliance a bit easier, and adhere to things like the SCC to safeguard data transfers across borders.
Of course, your app’s individual privacy policy and practices will ultimately determine whether you’re compliant, but that’s the same case regardless of the approach you take…
It's more keeping track of the replaceable moving parts and keeping your users in the loop plus what complying with consents they've given than data storage I'd imagine having issues with.
I could very well be wrong, it just sounds like more work than getting someone to code you up something. I could also care too much, worst case you'd get a slap on the wrist for a first offence (although I personally follow GDPR for moral reasons as well as legal, I am aware others don't care haha)