When we started Kuwinda we were building against a pretty loose set of possible use cases.
Ultimately this caused us to build a wide range of underdeveloped features rather than a narrow slice of product magic.
However, as the chinese proverb says “A journey of a thousand miles begins with a single step” this first rough cut build was our first step.
We have slashed our first version product down to focus on doing one thing well for a specific initial use case:
Being able to CRUD data within a single or multi-database environment.
Bloody awesome tables
While we have a longer-term vision and ambitions in other areas, the key to initial success is for non-technical people to be able to CRUD data.
Our first version tables falls woefully short of what it really needs to be.
This before-after slider shows a comparison of what we have today vs. what we’re building (Left: Old, Right: New):
Other than the obvious UI improvement there are a number of new features:
- Mass select to delete
- Nested related tables
- In-line editing
- Ability to add and import data
- Referencing an ID to a related table to show meaningful data
There is a lot more to be done within tables. Labelling field names for users, adding multiple related fields.
This is an area that we’ll keep building until it’s completely done.
Connect to multiple databases
Almost all tech companies we talked to have either started to or aspire to a microservices architecture.
We had initially only envisaged connecting to a single DB. Connecting multiple DBs of different types will be a core focus.
Every single customer we spoke to have said that they need some sort of permissions system and/or that is an issue they are looking to solve with this type of product.
We’ve gone for something that is hopefully a good initial balance of control and simplicity.
We’re going to work through building the above features and then we’ll be testing with a small number of people. If that could include you then let me know.