Update to CrudKit and long term vision

The CrudKit project had it’s development halted for over 8 months due to some personal reasons. But I’m pleased to let everyone know that the project is back in active development.

I’m pleased to announce the next alpha release - version 0.2 which adds Validation support and some minor fixes. It’s interesting to note that all the new features for 0.2 was sent in by open source contributors. You can download the latest release here.

A little background

From 2010 to 2014, I was the co-founder and primary developer of RazorFlow which is a framework to build interactive dashboards. Unfortunately due to some issues, we had to shut down the company.

In 2010 to 2012, we had an experimental version of RazorFlow which allowed using PHP to build dashboards which worked with SQL and PHP. While this experiment was quite popular it was difficult to adapt to real-world databases and was discontinued. If you’re interested you can take a look at what we built. A lot of ideas were adapted from that experiment into CrudKit.

Long term plan for CrudKit

The vision I have for CrudKit is quite clear - it’s to abstract all the “boring” parts of building a CRUD interface, while still giving enough power and flexibility to match your exact use case.

Many people use tools like phpmyadmin and adminer, but if you want to do things like execute custom code on save, pre-process data, secure data or allow more complex features, you’re not going to be able to do that.

Additionally, a big part of my vision is to allow building full interactive custom pages with powerful logic, and CrudKit becomes more of a framework to build back-office/admin applications.

Also, the application is designed in such a way that in a few releases, you should be able to embed just the CRUD part into an existing app. Think just the “table and form” embedded with a few lines of JavaScript.

Finding the sweet spot for CRUD

When people have to work with databases, the solutions I’ve seen are often in two parts of the spectrum - build a frontend yourself or use a database admin tool.

Since not everyone’s needs are the same, people often prefer to build their own solution from scratch. This means that repeating the same functionality like pagination, validation, etc over and over again.

CrudKit’s mission is to:

  1. Find out what is common to everyone’s CRUD needs and build it very well.
  2. Be flexible and extensible enough, so you can adapt it to your exact requirements.

I look forward to building this, and would love your feedback, suggestions, issues and patches.

Built by Anirudh Sanjeev. CrudKit is distributed under the MIT/X11 License.