One of the most consistent feedback we heard from the people we have spoken to is:
They do not want to write SQL.
Either they don't know how to write SQL.
Or they find writing SQL such a pain.
So we came up with a different approach to selecting data—without writing SQL:
How christmas 🎄and birthday 🎂 together! @flutterflow with a supa cool update! 😎 Tomorrow @supabase support will be enrolled. 💚💚💚 This creates powerful new possibilities in combination with @webflow@getwized as well as @dashibase for an easy backend admin.
🆕 Support for enum data type
For example, you might have a customer status field with the following options.
Dashibase will automatically create a single-select dropdown for this field in the record view and populate it with the respective options.
Some updates on @dashibase ! We are cooperating with them to bring you easy admin panels for your supastarter app in the near future! 🚀
Stay tuned for more updates! dashibase.com/blog/dashibase…
October was a huge month for us.
We shipped 14 features and improvements, finally allowing developers to bring their own code.
We sped up the app and polished the user experience.
Anddd we got our YC interview and were rejected.
dashibase.com/blog/dashibase…
The ship doesn't stop.
In the past week, we shipped 9 quality-of-life improvements to help you manage users, content, and records better.
NINE!
Let's go through them together 👇
✅ Updated onboarding
Since we changed a few aspects of the user experience, we update the onboarding guide in the Get Started Here demo dashboard that new users get when they sign up for Dashibase.
For more, check out our weekly changelog: dashibase.com/changelog/
Also, we are currently working on:
🔸 adding a search box for faster searches
🔸 adding support for custom data types
More to come! 😉
x.com/dashibase/status/15903…
🔍 Search coming soon!
Search the table, not just individual columns.
Get to the customer record you need faster.
No more hacking filters to find what you need.
We are seeing some tech startups trying Dashibase for their customer support ops e.g. find customer id/records to provide support.
They need to search a lot, and our filters are so-so for search. So we are adding a search box to all tables.
We're already testing it internally!