VedaApps
Start free trial
Build an app

How easy is it to build an app? Let's build one.

A leave-request app: employees ask for leave, managers approve or reject, everyone gets an email. Eight steps, no code — or one conversation with AI.

Try it yourselfBook a demo
What we'll end up with
leave.yourcompany.com
My requests
Signed in as Priya · 14 days left this year
Ask for leave
DatesReasonStatus
12–14 OctFamily function Requested
2 SepDoctor visit Approved
18 AugTravel Rejected
Two ways to build it

Eight steps, all by clicking.

  1. 1
    VedaQL

    Create the table

    Starting from nothing? Create a database and a table for the requests. Already have one? Skip this step.

    • Columns: employee, dates, reason, status
    • Your table, in your database
    VedaQL · leave_db · new table
    ColumnType
    idnumber · key
    employee_idtext
    from_date / to_datedate
    reasontext
    statustext · default “requested”
  2. 2
    VedaQL

    Write the queries

    One query per thing the app does. Each one becomes an API endpoint — no backend code.

    • my_requests · new_request
    • team_requests · set_status
    VedaQL · my_requests.sql
    SELECT id, from_date, to_date, reason, statusFROM leave_requestsWHERE employee_id = {{employee_id}}ORDER BY from_date DESC;
    POST/my-requests/v1Tested
  3. 3
    VedaUI

    Create the portal and pick a look

    New portal, choose a ready theme, add your logo and colours. The builder shows the real look from the start.

    • Ready-made themes
    • Light or dark, your logo
    VedaUI · Settings · Design
    Clean
    Forest
    Night
    logo.png · Primary colour #006398
  4. 4
    VedaUI

    Connect the data and sign-in

    Add your endpoints as connectors. Sign people in with your company login, so the server knows who each person is.

    • employee_id comes from the sign-in, not the browser
    • Keys stay on the server
    VedaUI · Connectors
    POSTmy_requestsemployee_id = {{session.employee_id}}
    POSTnew_requestemployee_id = {{session.employee_id}}
    POSTset_statusmanagers only
  5. 5
    VedaUI

    Build “My requests”

    Drop a table for the person’s requests and a form to ask for leave. Point both at the connectors.

    • Table + form, dragged onto the page
    • The form refreshes the table when it saves
    Page · My requests
    My requests Ask for leave
    12–14 Oct
    Family function
    Requested
    2 Sep
    Doctor visit
    Approved
  6. 6
    VedaUI

    Build “Approvals” for managers

    Drop a board grouped by status, and add the approval steps: who may approve or reject, and whether a comment is needed.

    • Requested → Approved / Rejected
    • Only managers see the buttons
    Page · Approvals
    RequestedRavi · 12–14 OctMeera · 20 Oct
    ApprovedArjun · 2 Sep
    Rejected
    RejectApprove
  7. 7
    VedaUI · Automation

    Send an email when it’s decided

    “When a request is approved or rejected, email the employee.” A rule, an email template — no mail code.

    • Templates with the request’s details
    • Queue, retries and a delivery log
    Automation · Rule
    When
    a leave request moves to Approved or Rejected
    Only if
    the employee has an email
    Do
    send email “leave_decision” to the employee
  8. 8
    VedaUI

    Check and publish

    Open “Approvals” to managers only, run the check, and publish. Change your mind later? Roll back in one click.

    • The check finds open data and missing setup
    • Publish to your own web address
    Check portal → Publish
    Nothing found — looks good.
    Release 1
    leave.yourcompany.com
    Live
What you didn't have to do

The hard parts are already built.

Most of the time in a software project goes into the parts nobody sees. With VedaApps they come with the platform, so your time goes into how your business works.

Writing and hosting a backend
Building a login and session system
Coding permission checks
Wiring up an email service
Deployment scripts and servers
A separate phone version

The usual way

  • Write requirements, wait for a developer
  • Build the backend, login and permissions first
  • Every change is a new ticket and a new release
  • A new screen means more code to maintain

With VedaApps

  • The person who knows the process builds it
  • Sign-in, roles, emails and releases are ready
  • Change a page and publish — or roll back
  • A new screen is another page in the builder

Build this app in your trial.

Start a 7-day trial — the builder, VedaQL and the AI connection are all included. No card needed.

Start free trial Book a demo