DrawPI - Building an API in minutes

Utkarsh Singh — Sun, 05 Jul 2020 22:27:35 +0000

Build a good design, materialize a great idea, you still need data to play with your product.
Collect as much as data as you want, you still need to send it back to the client in a systematic, secure manner.
What do you call this systematic, secure manner? APIs.

You are most probably aware of the concepts of an API. You're just wondering how can you build an API in 2 minutes when there are literally 1000+ courses over the internet teaching the intricacies of building it through code that takes hours?!

Well, the short answer is: you design, we code. All you have to do is Create, Define, Declare.

Create a project.
Define a model (a simple database).
Declare your endpoints. Have a look at the Create page here. This single screen outscores the manual process of code writing for APIs. The right pane focuses on building each endpoint, while the left defines the properties for the entire API. Let's look at each component of the page in detail.

Creating a Project

A Project is equivalent to an API. When you create a project:

A domain for the API in the form of <your-username>-<projectname>.drawpi.com is created. This means your API is now hosted before you even began writing code or declared an endpoint.
A database for the project is created.
A project folder at DrawPI servers is created to add the automatically generated code as you design endpoints.

Creating a Collection

Collections modularize your API. Nothing affects the functionality of your API through this. This is just to assort endpoints into certain categories so they become easy to manage at the back-end, and easy to understand while developing the front-end.

Building a Model

Models is an informal term for your Database. At present, DrawPI supports only MySQL databases, so you can only define an SQL schema. (We are expanding and soon will be back with an option to choose MongoDB too, hence the name Models).
When you create a model, it is basically a table in your projects database. You can define all attributes for your model here.
Isn't it high time the world found a way to build databases without going into the dark terminal or a .sql file?

Creating an Endpoint

Here's the most amazing part. Creation of an endpoint. Now, a disclaimer first. Designing your endpoint may not enable you to design extremely complex enterprise-level APIs, but if you are smart enough, you can use the Condition Block to build endpoints that you need for your projects.
So let's first try to understand what happens in the code of an endpoint.

We define an endpoint.
Some data is sent along with the request by the client.
We perform some manipulations in the database, or perform a query.
Return a relevant data item or part of it.

This is the natural basic flow of an API for most projects.
The data that endpoints require is used from the data attached with the request object coming in. req.body, req.params, req.query, you might have heard of these objects if you are a back-end developer, which are used as payload in POST requests, /, /endpoint?key= respectively.
We need to expect this data in our endpoint code first. That's what we do in the Query and Request Block.

Next up, is the Condition Block. This defines what you shall do with the data. Basically, the code to run after an endpoint request is made by a client is generated based on the structure of the operations in this block. Using this block requires a separate blog post of itself, but let me tell you the basic operations here.
DrawPI currently supports CRUD operations. This means, you can use the Condition Block to perform any Create, Read, Update, or Delete Operations in your database.
All this can be done just by choosing the operation, and choosing the data which needs to be updated.
This is all you do to build an endpoint, the platform writes the code, and deploys it as soon as you click on 'Launch Endpoint', everything within seconds.

Given this process of building an API, how long do you think it would take you to build yours?
2 minutes? 5 minutes? 15 minutes? We don't expect you to spend more time than that on our Create Page anyway.

And that, is how you can build your API in just under 2 minutes!
Head over to drawpi.com to witness the revolution.

Who is DrawPI for?

Even though DrawPI is a project that could revolutionize back-end development, it is still in development. This means, you could benefit by making APIs if:

Your project is a simple one with a few DB tables and endpoints.
You are a front-end developer who wants to see their Android/iOS/Web App project with something more functional than dummy data.
You want to build a complex back-end, BUT wished that the plain basic setup code and trivial endpoints could write themselves.

I want to stress on the 3rd customer a little here. DrawPI could be used as a customized boilerplate for any bigger project which is too complex for this platform.
Let's say, I need to build a complex Library System that uses heavy security add-ons like authorization headers, session tokens and cookies - features not currently supported by DrawPI. I will need to write code manually for these.
But, I could build models and define basic endpoints like getting info about a student, about a specific book, querying books in a specific category, etc. using DrawPI tools, and export the code to build on manually. Just imagine how much time a back-end developer saves by simply getting the setup done and trivial endpoints built.

Meet Jarvis Workspace Manager

Utkarsh Singh — Tue, 30 Jun 2020 12:49:06 +0000

Are you the kind of person who inevitably has to work on multiple tabs due to the complexity of your work?
We have all been there. You are researching about something, or building something, or doing any other task on your browser, and you end up opening at least 4 tabs if the task is simple, 10/12 tabs if the task is tough, or sometimes tabs you're too afraid to even count!
You know what opening so many tabs creates?
Chaos.
Yes, after a certain point, you don't even remember exactly on which tab is the information you looked at recently. You know everything that's going to help you is right in front of you, but you don't know where exactly.
And if a time comes when you have to disconnect from the work in progress, and maybe call the day or start working on some other thing, you are too much afraid to close these tabs.
Eventually, you start doing all the tasks on the same window, and mixing everything, or you open a new window and never really close anything.
One of these things is bad for your productivity while the other is bad for your memory.
A solution to get rid of this problem is saving Browser Workspaces.

There are many browser extensions, both in Chrome and Firefox that allow you to save a group of tabs as 'Workspaces'.

If you're a Chrome user, I suggest you use the following extension:
Workspace Launcher

During my time as a Chrome user, this extension really helped me to remain organized while doing multiple tasks.
Then I moved to Firefox, and (I guess) due to my poor searching skills, I couldn't find this kind of extension for Firefox. This gave me an opportunity to build my own extension! I could customize how it looked and overcome all the shortcomings I felt as a user in the Chrome extension that I used!
A week of learning and coding, and I was ready with my own Jarvis Workspace Manager!

The Jarvis-like Interface

Now, if you have read my previous blogs, you might know that I'm a huge fan of Iron Man.

Yeah, that's my home screen
By the way, here's how to do this to your PC if you're wondering: Jarvis, we love you 3000.

Anyway, so it was only fitting that I come up with an extension which makes it look like a JARVIS Interface is managing my Workspaces too!
So what do I need to achieve this? If I'm omitting the AI-enabled voice of JARVIS, then simply, a dark interface with a bluish green hue for the text and elements.
So that's what I did.

My current Workspaces in Firefox
So this is how it looks. Feel free to stalk your way in to what I do with my life. It'll also give you a better idea to know what kind of tab groups you should save as Workspaces.

Save tabs with just one click

In the Chrome extension that I used before, I had to manually enter all URLs that I wanted to be saved as a Workspace. That was a real pain if I had more than 5 tabs open!
So I made an enhancement:
All your open tabs are saved as one Workspace and you can carry on with your work seamlessly by one single click on the Extension icon!.
Of course, you can still add all the tabs manually too (the hard way), but I don't use that feature even though I had a good time coding it!

Having a map of your best links

If you save Workspaces for all your important tasks, you have an organized list of all your best important links in the new tab page automatically.
It's not necessary to open the entire set of all the tabs every time. Sometimes we just need to go to one of the links.
All such possible links will be right in front of you the whole time.
So you won't be just replacing your Mozilla default startup page with an extension's, it would rather be an improvement over the existing one.

Developer Support

Another good reason for its usage is that you know the developer who can solve the bugs for you and bring out new features on your informal request!
Github Repo

So all the best and I hope you use a Workspace Manager extension to organize your work, because believe it or not, you need it!

Forem: Utkarsh Singh