hyperbob n.

A living app document you can expand at any stage without rebuilding foundations; data, logic, and interface stay in sync.

Expand anytime. Share instantly. Connect everything.

Start building free See an example

The HyperBob Model

ONE LIVING SYSTEM

I

Plant

Describe your app. The roots take hold.

No framework to pick. No database to configure. Your data is the foundation.

Interconnected by nature

II

Grow

Add features anytime. The trunk holds everything together.

The reactive engine tracks every dependency. Nothing breaks.

Built to evolve

III

Branch

Logic, formulas, rules — they grow from what's already there.

Computed values extend the tree without rewriting the roots.

Evolves without rebuild

IV

Bloom

Live from the first edit. Share it, link it, connect it.

What users see and touch — always in sync, always shareable.

Shareable from the start

Why It Scales

"Add a like button"

Same prompt. Two very different development experiences.

Typical stack~30+ lines

// LikeButton.jsx
import React, { useState } from 'react';
import { useMutation } from '@tanstack/react-query';
import { api } from '../lib/api';

export function LikeButton({ postId }) {
  const [liked, setLiked] = useState(false);
  const [count, setCount] = useState(0);
  
  const mutation = useMutation({
    mutationFn: () => api.post(`/posts/${postId}/like`),
    onSuccess: (data) => {
      setLiked(true);
      setCount(data.count);
    },
    onError: (err) => {
      console.error('Failed:', err);
    }
  });

  return (
    <button 
      onClick={() => mutation.mutate()}
      disabled={mutation.isPending}
      className={liked ? 'liked' : ''}
    >
      {liked ? '❤️' : '🤍'} {count}
    </button>
  );
}

The HyperBob way6 lines

{
  "liked": false,
  "count": 0,
  "_view": { "el": ["button",
    { "set": [{"@@": "/liked"}, true] },
    [{ "if": [{"@": "liked"}, "❤️", "🤍"] }]
  ]}
}