11–20 of 40 posts
Love the domain "noloco.io", is this an intentional nod / reference to "SoMoLo" (as in Social, Mobile, Local) from the show Silicon Valley?
Love the domain "noloco.io", is this an intentional nod / reference to "SoMoLo" (as in Social, Mobile, Local) from the show Silicon Valley?
Do you have the capability to enable automated testing of the system built with the app builder? In my experience continued success with an app builder quickly becomes dependent on some testing capability to avoid breaking things over time. This is similar to unit/integration/system tests a "regular" developer would do, but trickier since it means making that available to users at a lower technical skill level. I'm i…
That's not something we currently offer, but it's certainly something I've thought about a lot. One of the benefits of no-code tools like Noloco is that you define, very explicitly, what your app should do, display and how it behaves under certain conditions. This really does allow for completely automated integration tests. such as verifying that a filter in the UI does filter the data, verify that when User X logs…
Earlier quoted context omitted.
That's not something we currently offer, but it's certainly something I've thought about a lot. One of the benefits of no-code tools like Noloco is that you define, very explicitly, what your app should do, display and how it behaves under certain conditions. This really does allow for completely automated integration tests. such as verifying that a filter in the UI does filter the data, verify that when User X logs…
I am not sure I follow your logic on why a low code tool should generate apps that don't need to worry about being tested. Even regular software _should_ function the way we tell it to but the point of testing is that sometimes this changes to no longer be true _unintentially_. If I generate a low code program with your tool that should have some desired behavior, but then someone makes changes it for it to do new th…
If you want to verify that it works how you want vs how it's setup to work, then you would be better leaning on existing tools that can do that.
My point about not needing to test it was about the implicit trust you would put in a platform like this, just like you would trust that a library you import behaves how it describes. It's not expected that you should write unit tests and integration tests to verify the behaviour of an external library
$240/mo for a starter plan is a bit salty for such a tool, isn't it?
How does this compare with some of the more 'enterprise' style tools like Alteryx? What would you say are the main differentiators?
In general, we tend to see that existing enterprise-focused tools tend to be more low-code rather than no-code and often more aimed at developers rather than non-developers.
Love the domain "noloco.io", is this an intentional nod / reference to "SoMoLo" (as in Social, Mobile, Local) from the show Silicon Valley?
Haha first time someone made that connection! It's more around no-code / low-code, but we also like how it means 'not crazy' in Spanish. Another benefit is that it's generally easy to spell as well, which loads of businesses have a problem with when it comes to search.
$240/mo for a starter plan is a bit salty for such a tool, isn't it?