Use Cases

Building Web Apps

DevLess is particularly good for building web applications. Some of the features that makes it easy includes automagically generated apis on creating tables by clicking and selecting over a user interface. With api endpoints available for each table created you can now feed this right into your web app. But then DevLess does not leave you there, it provides an HTML SDK . Yh! you heard me right an HTML SDK that allows the developer to get data by just writing plain old HTML . EG: To get data from a table labelled products all I have to do it add a DevLess directive to my tbody tag like <tbody class="dv-get-all:inventory:products"> DevLess will pull all the data from the products table under the service name inventory and display within the table. By the way services is a way of namespacing tables within DevLess. A service also comes with a script section which allowes developers to write rules to control the data coming and leaving the DevLess framework. For example if I wanted to captialize all names going to the database this is as simple as ->beforeCreating()->convertToUpperCase($input_name)->then->storeAs($input_name). To learn more or get started click me

Serve as backend for mobile apps

Building a mobile app involves not only writing code for the app itself but also the backend that handles data persistence and events like fireing up emails and handling long running tasks. Point is knowing how to build a mobile app is not enough you also need to either know how to build your backend or get someone to handle this for you.Its interesting how the majority of the backend frameworks we have are built as if everything we build is for the browser. For example most frameworks ship with HTML based error pages or lets talk about session storage that depends on the browser. Yes we can fine tune these frameworks to use for our mobile app but lets not forget we will still use the same backend for our web version as well. So why not have a framework that providez endpoints that is useful both for web and mobile? Most importantly why not make it easier so the mobile developer doesn't have to battle with all this backend stuff and just focus on the mobile app. This is exactly what DevLess does. On creating tables endpoints are generated and can be accessed via our mobile SDKs. Also in the event the developer has a need for some backend functionalities like sending emails you are able to install this right from our service hub. This is how mobile development should be. To learn more or get started click me

IOT Backend

So most IOT apps are hardware based. But then just like mobile apps IOT apps also need a place to persist data as well as run server based tasks. This is what DevLess is great for.All you need to do is fill out a form to create your tables and generate api endpoints instantly with which you can perform CRUD actions.Oh also you don't have to deal with these endpoints directly DevLess provides SDKs to help out with this. To learn more or get started click me

Central DataStore

Lets say for some valid reasons you need to write your app in mutiple languages. And you will need these components to talk to each other. DevLess makes this even easier. So Let DevLess connect to the database then pull in the data to any of the languages using the SDK for that language. Also by letting DevLess sit ontop of the Database you will be able to use the HTML SDK or JS SDK to query data right within your web app as well as manage privacy and authentication To learn more or get started click me

Adding functionalities to an existing app

DevLess has a service hub from where you can install backend functionalities with a single click. Now the interesting part is that you may use these installed services right within your frontend but also you can install it into any framework by pulling in the right SDK. This helps you reduce the number of dependencies you pull into your app. To learn more or get started click me