3: Building Your First App
      Back to home
      1. Home
      2. 3: Building Your First App

      Overview: Your First App Build

      A step-by-step introduction to starting your first application using the Rayven Workspace.

      Overview

      Rayven’s low-code platform enables you to build powerful, data-centric applications through a flexible and iterative process. This guide introduces the key stages involved in creating your first application in Rayven—from setting up your tables, designing workflows, and configuring interfaces, to adding users and testing the finished application.

      Whether your application is purely workflow-driven, built for operational dashboards, or has a fully interactive frontend, the first build follows the same foundational steps.

      Getting Started

      Before beginning your first app, make sure you're signed in at https://workspace.rayven.io.

      From the Workspace home page, you can initiate a new application in three ways:

      • Start with AI Blueprint – Let Rayven generate a base application using your description.

      • Start Building Now – Begin from scratch with full control over every configuration.

      • Create App (from the left-hand menu) 

      Each method results in the creation of a blank Rayven Application with its own tables, workflows, interfaces, and users.

      Accessing the App Page

      Once you create a new application, you’ll be taken to the App Page for that specific application.

      This is the central area from which you can access and manage all key components of your app:

      • Tables – Define your data structure

      • Workflows – Build your app logic

      • Interfaces – Configure user-facing screens

      • Application Users – Add users and control access

      At the top, you’ll see a four-step guide to walk you through building your application.

      Step 1: Create Your First Table

      All Rayven applications require a Primary Table to anchor structured data. This table holds the unique identifiers (UIDs) that the rest of your application logic references.

      At a minimum, your Primary Table needs:

      • One unique identifier column (UID)

      • At least one row of data

      Once the Primary Table is in place, you can optionally add Secondary Tables for supporting any additional data, child records, or lookups, logs etc.

      You can configure data types, label columns, key columns, and linking options directly from the Tables page.

      Step 2: Build a Workflow

      Next, build the core logic of your application using the Workflow Builder. Each application needs at least one workflow, which defines how data flows, transforms, and is visualised.

      You can add:

      • Connector Nodes to ingest or output data

      • Logic Nodes to transform or calculate values

      • AI Nodes to access Generative AI intelligence

      • Frontend Nodes to display visualisations

      • JavaScript Nodes for advanced logic

      • UI Code Nodes for building custom widgets

      Workflows process data in real time and can be run once, for every UID in the Primary Table, or for label-based groupings.

      Step 3: Add Interface Pages

      Interfaces are the front-end screens users interact with. Each interface contains one or more widgets, which come from the Frontend nodes used in your workflows.

      There are two types of interfaces:

      • Standard Interface – For most dashboards and interaction pages.

      • Analytics Interface – Adds date filtering for time-series and historical views.

      You can also choose:

      • Top-Level Interface – Appears in the app’s main navigation menu.

      • Drilldown Interface – Only accessible by clicking into a widget.

      Interface layout is configured by admin users on the front-end, not in the Workspace.

      Step 4: Add Application Users

      Application Users access the front-end interfaces. You’ll need to:

      • Create User Groups

      • Optionally assign Label-based data filters (Note: By default, new user groups are created with the filter PrimaryLabel=All, which grants access to all Primary Table rows. You can edit this if you need to restrict access.)

      • Specify which Interfaces the group can access

      Setting up a User Group:

      Selecting which interfaces the User Group can see

      Each user must belong to a User Group. Permissions (like Editor or Viewer) determine their capabilities on the frontend, including whether they can move widgets or download data.

      Step 5: Publish and Test

      Once your tables, workflows, interfaces, and users are in place:

      • Sign in as an Application User at https://app.rayven.io

      • Test the interfaces, data flows, and visualisations

      • Adjust logic or layout based on feedback

      You can return to the Workspace at any time to iterate and improve your application. Rayven applications are modular and built to evolve.

      Summary

      Building your first app in Rayven is a structured process that gives you full control over data, logic, and user experience. The platform’s flexibility allows you to start simple and grow into more complex use cases over time—whether you're building frontend-heavy tools or backend workflow engines.

      Key takeaways:

      • Begin with a Primary Table to structure your data

      • Use workflows to process and move your data

      • Create interfaces and widgets to visualise and interact with your data

      • Assign users and control access using User Groups

      • Test and refine iteratively through the Workspace

      FAQs

      How many workflows can my first application include?
      There’s no limit—you can start with one and add more as your logic and needs grow.

      Can I use Rayven without creating a user interface?
      Yes. Rayven supports fully workflow-based applications that don’t require front-end interfaces. These are ideal for automation, integration, and backend logic.

      What happens if my Primary Table is empty?
      Every application requires at least one row in the Primary Table. Without this, workflows and interfaces won’t function as expected.

      Do I have to use AI when creating an app?
      No. Starting with AI Blueprint is optional. You can build every element manually using the Workspace tools.

      Can I preview my application before publishing?
      Yes. Application Users can test the live interfaces immediately once they've been given access. No formal "publishing" step is required.