mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
f4ee7a0525
Bylines, paper authorship, correspondence addresses and the founder blurb under each post named an individual. They name the organisation that published the work instead: the brand on posts and pages, the research byline on papers, and research@ in place of a personal address. Both are what these repositories already used elsewhere — nothing new was coined. Co-authors are untouched. Where a paper named someone else alongside, they stay named; only the one byline changed. Bibliography entries, running heads, PDF metadata and affiliations move with it, so a citation still resolves to whoever the cited paper names. Sample and fixture data uses the placeholder name these tests already use elsewhere, so no assertion changed meaning.
96 lines
3.2 KiB
TeX
96 lines
3.2 KiB
TeX
\documentclass[11pt,a4paper]{article}
|
|
\usepackage{../shared/luxcover}
|
|
\usepackage[utf8]{inputenc}
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage{amsmath,amssymb,amsfonts,amsthm}
|
|
\usepackage{graphicx}
|
|
\usepackage{hyperref}
|
|
\usepackage{algorithm}
|
|
\usepackage{algpseudocode}
|
|
\usepackage{booktabs}
|
|
\usepackage{multirow}
|
|
\usepackage{array}
|
|
\usepackage{xcolor}
|
|
\usepackage{float}
|
|
\usepackage{enumitem}
|
|
\usepackage{mathtools}
|
|
\usepackage{listings}
|
|
\usepackage{tikz}
|
|
\usetikzlibrary{arrows.meta,positioning,shapes.geometric}
|
|
|
|
\newtheorem{theorem}{Theorem}
|
|
\newtheorem{lemma}[theorem]{Lemma}
|
|
\newtheorem{proposition}[theorem]{Proposition}
|
|
\newtheorem{definition}{Definition}
|
|
\newtheorem{corollary}[theorem]{Corollary}
|
|
\newtheorem{remark}{Remark}
|
|
|
|
\hypersetup{
|
|
colorlinks=true,
|
|
linkcolor=blue,
|
|
citecolor=blue,
|
|
urlcolor=blue
|
|
}
|
|
|
|
\lstset{
|
|
basicstyle=\ttfamily\small,
|
|
breaklines=true,
|
|
frame=single,
|
|
xleftmargin=1em,
|
|
framexleftmargin=0.5em,
|
|
columns=fullflexible,
|
|
keepspaces=true,
|
|
showstringspaces=false
|
|
}
|
|
|
|
\title{\textbf{The Firebase Exit: Migrating Cloud Apps to Local-First Cryptographic Architecture}\\[6pt]
|
|
\large From Vendor Lock-In to Sovereign Capsules\\on Lux Network}
|
|
|
|
\author{
|
|
Lux Research\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{2025}
|
|
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
Firebase, Supabase, Convex, and Notion represent the state of the art in
|
|
developer experience for cloud applications: real-time sync, authentication,
|
|
serverless functions, and managed hosting in a single SDK. They also
|
|
represent the state of the art in vendor lock-in: the provider owns your
|
|
data, your auth identities, your function runtime, and your users' data
|
|
sovereignty. This paper presents the Firebase Exit---a systematic migration
|
|
path from cloud-dependent application architectures to local-first
|
|
cryptographic applications (capsule apps) on Lux Network. We define a
|
|
component-by-component mapping from Firebase/Supabase primitives to their
|
|
capsule equivalents: Firestore becomes encrypted SQLite with CRDT
|
|
synchronization, Firebase Auth becomes I-Chain decentralized identifiers,
|
|
Cloud Functions become Base Functions executing in the capsule's trust
|
|
boundary, and Firebase Hosting becomes the decentralized provider market.
|
|
We provide a step-by-step migration guide, benchmark local SQLite reads
|
|
against Firestore network round-trips (showing $10\times$--$100\times$
|
|
latency improvement for reads), analyze the offline-first advantages for
|
|
mobile and edge deployments, and present four case studies (notes app, CRM,
|
|
team chat, project management) demonstrating that every Firebase app can
|
|
become a sovereign capsule app with equivalent functionality and strictly
|
|
superior data ownership, privacy, and portability.
|
|
\end{abstract}
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-what-firebase-gets-right}
|
|
\input{sections/03-what-firebase-gets-wrong}
|
|
\input{sections/04-migration-mapping}
|
|
\input{sections/05-step-by-step-migration-guide}
|
|
\input{sections/06-performance-comparison}
|
|
\input{sections/07-offline-first-advantages}
|
|
\input{sections/08-case-studies}
|
|
\input{sections/09-related-work}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|