Introducing Webase

One of my daughters recently asked me if we could build a tree house.  She is very imaginative and has asked me to help build lots of things that were way beyond my skillset.  So when she asked for a tree house, something I felt was within my ability, I said, "Sure honey.  Let's do it!!"

I encouraged her to help with the process.  She drew up some designs, went to Lowe's with me, and helped haul lumber into the back yard.  We planned the work and then worked the plan.

Here is a shot of it about mid-way through.

My daughters tree house project, 1/2 way through.

I did most of the difficult work, but my daughter helped and I hope she will feel empowered from this experience.

Similar to my treehouse project, Webase is a platform enabling you to build software.  I am putting two decades of software development experience into a tool that will do the heavy lifting and empower you to create real applications without having to write code.

Also like the treehouse, the design of Webase is intended to be simple and sturdy.  So the things you build just work.  Over time we will add polish and sophistication, but currently we are working on the foundation.

Webase version 1.oh

The current version of Webase allows you to create applications that can create, update and display data [1]. 

You create an App by simply giving it a name and then create your "data model" by adding Tables to your App.  Tables, also referred to as Models (as in data models the not super models variety like Cindy Crawford), is where your data is grouped together and stored.

Think of these models as real world things or ideas your app cares about. 

Some examples may help.  For a project management app, you could have a Projects table and a Tasks table. 

For a blog app, you could have a simple Posts table that encapsulates the Title and Content of each post.  Incidentally that is exactly what this blog you are reading now is: a simple custom app built on Webase [2].  Cool right?

Tables have value because of the fields that you add to them.  Think of fields as specific aspects of the data model you are interested in.

In our project management app, the Tasks table could have the following fields: Title, Description, Assigned To, Due Date, Completed.  Each of these fields hold different pieces of data to create the concept of a task.

As a final example, an early user of Webase, recently created an app for managing outfits for different seasons.  This is something I would have never thought of, and why I am so excited about building this platform.  

Everyone deserves to be able to build things that suit them.  And business should not always have to conform their business processes to some archaic tool;  they should be able to easily add fields for new data they want to capture and have tools that unlock new realities for them.

How Webase Works

I know you are eager to actually get to the tool!  Here are the steps to building a simple but useful application on Webase.

  1. Create an app
  2. Create one or more tables
  3. For each table create some fields.

Then you can "open" your app and start using it to create, update and display your data.  Webase will auto-generate the views to support this.

You can return to the App Editor anytime you want to edit the app to add new fields or create a new table.

I'm a Little Embarrassed

I have a confession to make.  I am a little embarrassed about this early version of Webase.  The tool looks a little bit like the tree house picture above.  It is simple and rudimentary. 

So why am I shipping it and telling the world about it?

Simple.  I have a problem.  

I can build things for weeks and weeks.  The weeks turn in to months and the product never gets finished.  It is never good enough.  I never get feedback on it.  And the tool dies a quiet death, in the woods of a git repository, and no one ever cares.  It is a sad waste of time.

So Webase will be different.  It will represent my best work as a software developer.  And I am forcing myself to talk about it all along the way.  To find out early and often if it is solving real problems for real people.

Toward this goal I will give public updates on progress of both the product and traction.  If you are interested in seeing how to grow a new platform literally from ground-level, sign up and you'll get periodic updates.

Here is what the current Roadmap includes:

  1. Better design (this will be an ongoing process.... let me know if you'd like to help! :-)
  2. App templates (starter apps that solve common problems)
  3. A Marketplace (so users can publish their own applications)
  4. Support for attachments (Currently supported in a Text field as you can see in this blog post, but we need it as a field type too)
  5. Support for customizing views
  6. Support for filtering data
  7. And much much more! :-)

Thank you

Thank you for taking the time to learn a bit about Webase.  In todays world, just the five minutes you invested here means a lot to me.  I sincerely hope the return it back to you multiplied, either by the platform or things you learn as I share this journey with you.

Please reach out if you need or like any help.  Just signup and you'll get my email!

I can't wait to see what you build!  

[1] Technically it supports a CRUD interface which stands for Create, Read, Update, Delete and is a common term in computer parlance for how applications deal with data.

[2] This blog is an app that was created on Webase.  It has the following fields: Title (String), Published (Boolean), Category (Single Select) and Content (Text).  I have also made it publicly readable meaning you can see the content but cannot create or update the data.