Build and connect your frontend
LobLogix builds the backend. The frontend is yours to choose, in any framework, built by you, your team, an agency or an AI coding tool.
LobLogix builds the backend of your application. The frontend, meaning the screens people use, is yours to choose and to build: in any framework, by you, your team, an agency or an AI coding tool.
Why it is split this way
The backend holds what has to be right: your records, your rules, who may do what, and sign-in. It is agreed in writing and checked before release. The frontend is what people see, and it changes more often. Because the backend enforces the rules itself, a screen cannot get around them, whoever or whatever built it.
Your choices
- The framework. React, Svelte, Vue, Flutter or anything else that can call a web API. Web, mobile or both.
- Who builds it. You, your team, an agency, or an AI coding tool that you direct.
- Where it runs. Wherever you host it. LobLogix does not host the frontend.
What you hand to whoever builds it
- The description of your backend. An OpenAPI document that lists every record and every action available over JSON:API, and a GraphQL schema for GraphQL. Developers read them, and AI coding tools read them well.
- Its address in Stage. So the frontend can be tried against a running backend with test records.
- How people sign in, and the roles. Both are decided in your specification.
See What a developer receives from LobLogix.
Building it with an AI coding tool
- Give the tool the OpenAPI document, or the GraphQL schema if it works with GraphQL.
- Ask for one screen at a time, in the words of your Living Spec.
- Try each screen against Stage, with sample records.
- Try what should be refused. The backend says no, and the screen should show why.
What the backend guarantees, whatever the frontend
- A rule that refuses a bad entry refuses it from every screen.
- A person sees and changes only what their role allows.
- Sign-in is enforced by the backend, not by the screen.
What LobLogix does not do
It does not build, host or check your frontend, and it cannot vouch for what an AI tool writes. Check the screens the way you would check any work: against what you agreed.
In the alpha
You can connect your own frontend to your application in Stage, and try the same application in plain words with Ask My Backend. See Ask My Backend: try your application in plain words. Use sample records only.