Category: Uncategorized

  • Surfaces, Not Pages

    Introduction

    One of the recurring questions in Elonn is how we should interact with the existing web.

    At first glance, the answer appears simple. If a user searches for coffee, restaurants, events, products, or businesses, many of the results will ultimately be web pages. The obvious solution is to open those pages in a browser.

    The problem is that Elonn is not being designed around browsers. Today we have web, Android, and iPad runtimes. Tomorrow we may have XR headsets, vehicle displays, voice interfaces, wall displays, and devices that do not yet exist. Requiring every runtime to become a browser would force the entire platform to inherit the assumptions of the web rather than defining its own.

    The opposite extreme is equally unattractive. We could strip away all presentation, extract the text, and reduce every website to a plain content object. While technically simpler, that approach discards much of the value created by publishers and designers.

    The goal should not be to preserve pages. The goal should be to preserve intent.

    The Wrong Question

    The traditional question is:

    “How do we display a web page?”

    That question assumes the page is the fundamental unit of the web.

    Increasingly, that assumption is false.

    Modern websites are rarely authored as monolithic documents. They are assembled from components, sections, blocks, widgets, modules, and reusable content structures. WordPress, Shopify, Webflow, React, Vue, Elementor, Gutenberg, Divi, and countless other systems already treat pages as compositions rather than indivisible artifacts.

    A coffee shop website may contain:

    • A hero section
    • A location section
    • An hours section
    • A menu section
    • An events section
    • A gallery section
    • A contact section

    The browser presents these as a single page because that is the browser’s only presentation model.

    The underlying structure is already much richer.

    The more useful question becomes:

    “What meaningful objects exist within this resource?”

    From Pages to Surfaces

    Elonn should treat web pages as containers rather than destinations.

    When Find discovers a web resource, it should not immediately become a runtime object. Instead, the resource should pass through a translation layer.

    The translator examines the resource and identifies meaningful surfaces.

    A restaurant page might produce:

    • Business Surface
    • Hours Surface
    • Menu Surface
    • Events Surface
    • Gallery Surface
    • Contact Surface

    A news article might produce:

    • Article Surface
    • Author Surface
    • Related Resources Surface

    A conference website might produce:

    • Event Surface
    • Venue Surface
    • Schedule Surface
    • Registration Surface

    These surfaces become first-class objects within the platform.

    The page is no longer the object.

    The page is a source of objects.

    Preserving Design Without Preserving HTML

    A common objection is that this approach appears to discard the work of web designers.

    In reality, the opposite may be true.

    Much of a modern website exists to satisfy browser requirements rather than user requirements.

    Navigation systems, cookie banners, advertising containers, analytics scripts, SEO structures, responsive layout systems, framework scaffolding, and numerous other elements are necessary because the browser requires them.

    Users rarely seek those things.

    What users value are:

    • Branding
    • Visual identity
    • Photography
    • Information hierarchy
    • Tone and voice
    • Content
    • Functionality

    Those elements can survive translation.

    A Business Surface might preserve:

    • Logo
    • Brand colors
    • Hero image
    • Business name
    • Description
    • Contact information
    • Hours
    • Links

    An Article Surface might preserve:

    • Publisher attribution
    • Author attribution
    • Hero imagery
    • Typography preferences
    • Content hierarchy
    • Citations
    • Provenance

    The exact HTML implementation disappears.

    The publisher’s intent remains.

    This distinction is critical.

    We are not preserving browser implementation.

    We are preserving publisher intent.

    The Evolutionary Path

    The most promising aspect of this model is that it does not require the web to change overnight.

    Initially, Elonn can infer surfaces through translation.

    HTML becomes source material.

    Structured data, schema.org metadata, OpenGraph information, accessibility landmarks, content hierarchy, and component patterns provide clues about the meaningful objects contained within a resource.

    Over time, publishers can assist the process.

    A WordPress plugin could allow site owners to explicitly identify surfaces.

    A Gutenberg block might be marked as:

    • Hours Surface
    • Menu Surface
    • Event Surface

    A Shopify section might be marked as:

    • Product Surface
    • Store Surface

    A Webflow component might be marked as:

    • Contact Surface
    • Gallery Surface

    Eventually, publishers may provide Surface Manifests directly.

    At that point the website itself becomes only one possible rendering of a collection of surfaces.

    The relationship reverses.

    Today:

    Surface is derived from Page.

    Tomorrow:

    Page is derived from Surface.

    Implications for Elonn

    This approach aligns naturally with the broader Elonn architecture.

    Find discovers resources.

    Surface translates resources.

    Runtimes consume surfaces.

    The runtime never needs to understand HTML.

    The runtime never needs to execute arbitrary JavaScript.

    The runtime never needs to become a browser.

    Instead, every runtime consumes the same set of portable objects.

    A menu can appear in a mobile application, a field view, an XR headset, a vehicle display, or a future device without modification.

    An event can be attached to a conversation, placed in a field, shared with a community, or surfaced through discovery.

    A business can exist as an object rather than as a page.

    This transforms the web from a collection of destinations into a collection of reusable components.

    Conclusion

    The future opportunity is not to replace websites.

    It is to expose the structure that already exists within them.

    The modern web has spent years moving from documents toward components. WordPress blocks, Shopify sections, React components, and countless other systems have already decomposed pages into meaningful parts.

    Elonn can build on that evolution rather than fighting it.

    The platform does not need to destroy the web developer profession. It can extend it.

    Instead of designing pages for browsers, creators can gradually design surfaces for a network of runtimes.

    Pages become one presentation layer among many.

    Surfaces become the primary unit of information.

    The result is a system that respects the work already invested in the web while creating a path toward a more portable, reusable, and device-independent future.

  • The Next Evolution of the Internet Is Not Another App

    The Next Evolution of the Internet Is Not Another App

    Every few decades, the underlying model of computing changes.

    Mainframes gave way to personal computers.
    Desktop software gave way to the web.
    The web gave way to mobile.

    The next transition has already begun.

    Spatial computing.

    Right now, the industry is where mobile phones were when Motorola installed them in car trunks.

    The hardware is early.
    The interfaces are primitive.
    The ecosystem is fragmented.

    Most current XR experiences feel disconnected because the foundational infrastructure for a persistent spatial internet does not exist yet.

    That is the problem Elonn solves.

    Apple, Meta, Samsung, Google, and countless startups are all moving toward a future where digital information exists around us instead of trapped inside flat screens.

    But most companies are still building isolated applications tied to specific hardware platforms.

    Elonn is being built differently.

    Elonn is a layered world for the next era of computing.

    A persistent digital environment composed of services, social systems, discovery systems, collaborative spaces, and adaptable runtimes that can evolve across many classes of devices.

    The architecture matters.

    Elonn separates services from runtimes.

    Services persist.
    Runtimes evolve.

    Today we have early runtime demonstrations for web and Android that validate this direction.

    Tomorrow there may be runtimes for headsets, glasses, vehicles, desktops, wearables, walls, and devices that do not yet exist.

    When new hardware arrives, Elonn does not need to reinvent the ecosystem.
    A new runtime connects to the existing layered world.

    That flexibility dramatically changes how quickly the platform can evolve alongside the market.

    Elonn also provides persistent identity.

    A person’s identity persists across services and runtimes so their relationships, communities, permissions, conversations, installed services, and digital environments remain part of the same world regardless of device.

    The identity belongs to the person.
    Not the device.
    Not the runtime.
    Not a single application.

    Social structure is central to Elonn.

    Most modern platforms are built around attention extraction.

    Their systems reward outrage, engagement spikes, follower accumulation, endless scrolling, and algorithmic amplification because those behaviors maximize advertising exposure and platform retention.

    The result is a digital environment optimized to manipulate attention instead of strengthen relationships.

    Elonn is built differently.

    Elonn uses circles.

    Circles are based on relationship proximity and trust, not popularity.

    The people closest to you socially occupy your inner circles.
    Communities create additional context.
    Conversations and gatherings inherit visibility and relevance from actual human relationships instead of engagement algorithms.

    A message from someone close to you carries more significance than content artificially boosted by outrage metrics.
    A gathering shared through trusted communities behaves differently from a globally promoted event.
    A conversation inside a private community remains contextual instead of being pushed into mass visibility.

    The system is not designed to maximize addiction loops.
    It is designed to maximize relevance, trust, and meaningful interaction.

    That distinction becomes critically important in a spatial world.

    As information moves beyond flat screens and begins existing persistently around us, filtering can no longer depend on engagement algorithms optimized for advertising.

    People need environments shaped by human relationship, trust, and contextual relevance.

    Circles provide that structure.

    We also built Find.

    Find is not a traditional search engine and not an infinite content feed.

    Find is a discovery system for a layered world.

    People use Find to discover:

    • communities
    • gatherings
    • conversations
    • places
    • services
    • collaborative spaces
    • vendor-built experiences

    Instead of reducing discovery to lists of links and algorithmic feeds, Find presents information contextually through spatial panels, side rails, layered environments, and persistent shared spaces.

    Panels rotate into view.
    Shared workspaces persist.
    Information becomes navigable space instead of isolated pages.

    The goal is not to trap attention.

    The goal is to help people navigate a richer digital world more naturally.

    The interface model itself changes.

    Phones flatten information into apps and feeds.
    Desktop systems isolate information into windows.

    Spatial systems allow information to exist around you.

    Elonn is designed for that future.

    Panels are designed to be shared.
    A panel is not merely a window.
    It is a social object.

    People can collaboratively inhabit spaces containing maps, browsers, conversations, schedules, research, media, productivity systems, and vendor-built services simultaneously.

    The architecture assumes cooperative presence rather than isolated application usage.

    Importantly, Elonn is not intended to become a closed ecosystem.

    Vendors and developers will be able to build services users can install into their world.

    Educational systems.
    Productivity systems.
    Mapping systems.
    Community overlays.
    Collaborative environments.
    Entertainment systems.
    Entire categories that have not yet been invented.

    Those services become part of the layered world and remain consumable across multiple runtimes and future devices.

    We do not believe Elonn will be the only major player in this transition any more than AOL, Yahoo, Netscape, or AltaVista were the only important companies of the early internet era.

    But every platform shift creates opportunities for new infrastructure, new interaction models, and entirely new ecosystems.

    We believe spatial computing represents one of those moments.

    The transition now underway is larger than headsets.

    It is the evolution of the internet from pages and applications into layered persistent worlds.

    Elonn is being built for that future.