Hi Noloco team,
First of all, please know that this comes from a place of love. Fantastic team, fantastic product. But, it’s not perfect (obviously), as no product is. But lately, there have just been a noticeable increase in bugs…
- Workflows not firing for long periods of time or not firing at all,
- Very simple workflows erroring with no discernable reason
- Permissions failing to save with an indecipherable error warning
- Random “there are issues with your app” pop-ups that offer you to “fix” your issues and after loading goes away
- Not being able to use certain static dropdown values in Ul visibility conditions
- Inconsistencies in light vs dark mode, for example the backlink element wasn’t visible in dark mode
- Simple field name changes breaking things in Noloco with the only solution being the engineers fixing something on their end
- Filters in Noloco Tables not applying to the data until you undo it, then reapply the filter a second time
- DocsAutomator integration breaking which crippled one of my client’s sales teams for like 4 or 5 days, and many other issues
What has surprised me most, is that several of these issues have been resolved in the past, and have come back (like not being able to choose a static dropdown value within certain Ul visibility conditions).
Yes, some of my issues ended up being user error due to edge-cases or overlooked permissions configs on my end, but the majority have not been user error. Additionally, most of the issues have come up when working with Noloco Tables as the app datasource. I find that building with it takes probably 2x longer than building with Airtable, is significantly less reliable (e.g. the bugs above), and is very limiting for many use-cases compared to what you can do when using Airtable as the backend.
As a side note, apart from “Get record” and “Create record”, the Make integration feels very incomplete (the mappable outputs when working with Noloco Collections are messy and seem unstructured, I’ve run into many errors), and most critically you can’t work with files apart from tapping into your app’s GraphQL API. I realize this point is not in-line with my post’s title, but is rather more of a subpoint that a lot of your customer base would probably love a bit more attention to polishing core functionality and integration basics.
One of the biggest friction points for me which is honestly dampening my experience as a service provider and impeding my efficiency is that tickets often automatically close after only 3 days which leads your customers and service providers to create a duplicate ticket for that same issue since the original conversation auto-ended. I can’t count how many times l’ve created duplicate tickets in the last three weeks or so, and I can’t afford to spend time re-creating context/tickets for the support team, and I’m sure it’s also a headache for your team to receive multiple tickets for the same issue and customer.
Lastly, I was apprehensive about posting this (and originally deleted it) because I really think Noloco is a fantastic no-code app builder, and my personal favorite. I don’t want it to come across with a sour tone or push people to move away. I also didn’t want to post this and potentially be the only one saying these things, however I’ve recently received validation from others experiencing the same things. For example, one person told me that in recent weeks their Noloco app is riddled with bugs and overall performance and reliability are “falling apart” (that’s probably a bit dramatic, as my own clients still have their apps running even through the bugs, and their businesses remain operational, apart from one particular bug in the last week that broke half of my client’s app for several days 
)
I’ve been excited to see some of the recent feature releases (Spaces, Stripe, and more) but am starting to care less about those given some of the fragility I’m feeling this year around the core functionality. Again, Noloco is my favorite, but at the end of the day the stark difference in building in a platform like Glide is that I almost never run into bugs. I believe I can recall one single bug in my experience building apps with Glide.
I think at the end of the day I’m just curious if other things are going on under-the-hood that are upstream from these issues, like changes or experimentation from the dev team, and if there’s clear direction on the roadmap for addressing some of the product’s apparent fragility. It’s been a very rocky quarter and l’d love to hear if something can be done about the automatic ticket closure, and if any extra insight can be provided into anything above!
Thank you so much!
