Feature Roadmap

We wanted to be 100% transparent with what we’re working on. So below is all of the features we currently have as well a what we’re working on now and thinking about next.

What can Kuwinda do today?

Dockerised install

A dockerised install was important for us because we wanted to make it super easy to install Kuwinda. If you have Docker installed we’ve managed to get it down to three commands which we’re pretty happy with. If you don’t there’s an extra two.

We’ll be looking to get it into package installers in time but this was a good first step.

Connect to a database and auto-detect schema

One of the first steps is for Kuwinda to be able to connect to a target application’s database. This will allow it to CRUD data depending on how you set it up.  As a starting point we’ve included support for MySQL & PostgreSQL We’ll add support for more databases later.

Once the database is connected the application looks at the schema and lists out the available tables. It uses the schema to reference related fields in tables and views that you can build, see tables or views lower down.

What we’re working on right now

Users & User roles

Our first couple of users who wanted to use the app had a need to be able to add multiple users and have some user permissions. We’ve started working on this as it’s a lot easier to have role based permissions in from the start.

Here’s the design for the main permissions access control which will be set per connected database.

Connect to multiple databases

Given we live in a world where apps and internal systems have many databases we’ve been asked to enable multiple database connections. This makes sense given the needs of apps with microservices architectures and businesses with multiple apps.

 

Supercharged CRUD Tables

A key starting point is to be able to view and interact with a table of data.

We’re building:

  • Indexed search: So that you can search across all fields and rows in a table;
  • Show/hide columns: Allowing the table to be customised from fields in the table;
  • A-Z / Z-A sort: So that you can organise by date/in order;
  • Reorganise column order: So that the data is in an order your users will understand;
  • Export to CSV: To allow external manipulation;
  • Inline editing: To update records;
  • Multiple select: To delete multiple records;
  • Nested tables: To show data from related tables;

What we’re thinking about next

More Tables Features

Once we get the first cut of CRUD tables out we’re going to be looking at how we can improve them.

This could include

  • Being able to show related data: IDs in a table should reference the row(s) in the relevant table. So that if you’re looking at a User say John that you see he’s booked The red room instead of ID 192;
  • Different things to nest within tables;

Have a suggestion? Join us and let us know…