Try app

Pick the fastest path into PARA.

Use the live public host when you want immediate access, request a build link when you need a handoff package, or bring the whole stack up locally when you need full control.

This page gathers the practical ways to get into PARA: open the current experience, ask for a build link, or understand the local setup without hunting through scattered notes.

Open shared host Download Android APK

Shared host ready Android APK hosted Local stack commands below

Access paths

Shared host

Open the live public build now

Best when you want to inspect the current civic surfaces without waiting for a new package.

Android APK

Download the current Android package

Best when you need the latest hosted Android binary without waiting for a manual handoff.

Run locally

Bring the stack up from source

Best when you need full control over the app client, AppView, and PDS while testing.

Current runtime

Shared demo host

https://web.paramx.social.ngrok.pro

Shared PDS host

https://pds.paramx.social.ngrok.pro

Workspace split

Expo client in PARA, backend stack in watx, docs site in website.

Fastest path

Open the shared host or download the current Android APK directly.

Android package

https://pub-dfee4e25e68c4ca397417416b1307bde.r2.dev/para-android-latest.apk

Android package

Android build is hosted. Use the request draft for anything else.

The current Android package is available directly. Keep the request draft for iOS, private tester handoffs, or when you need a newer internal build than the hosted APK.

Which platform you need: web, iOS, Android, or all three.
Whether you want the current shared build or a newer internal package.
Who should receive the link and what team or use case it supports.
How quickly you need it so the handoff can be prioritized.

Fallback request

Use the hosted APK first, then fall back to this request.

Hi PARA team,

I'd like access to the current build link.

Name or team:
Platform:
How I want to test PARA:
Preferred turnaround:
Who should receive the build:

Thanks.

The request template stays useful for non-Android requests and for newer internal packages.

Download Android APK

Run from source

Bring up the docs site and the PARA app separately.

The public site and the app client live in different workspaces, so they start separately even though they support the same demo story.

Docs site

SvelteKit site in website

App client

Expo web client in PARA

Backend

PDS and AppView stack in watx

Docs site

cd /Users/mlv/Desktop/MASTER/website
pnpm install
pnpm dev

PARA app client

cd /Users/mlv/Desktop/MASTER/PARA
yarn
yarn web

Why this split exists: the website repo serves the public docs and marketing site. The PARA repo is the actual app client.

Backend path

Bring up the backend the way the current runbooks describe it.

The backend development flow in watx is the part that expects Docker. This is the short path that matches the repo runbook.

cd /Users/mlv/Desktop/MASTER/watx
make nvm-setup
make deps
make build
make run-dev-env

PLC

http://localhost:2582

PDS

http://localhost:2583

AppView

http://localhost:2584

Persistent shared demo

cd /Users/mlv/Desktop/MASTER/watx
cp -n .env.shared-demo.example .env.shared-demo
make run-dev-env-persistent

The shared-demo runbook advertises the public identities as https://pds.paramx.social and https://appview.paramx.social.

Production-style serve

Build and serve the web app bundle from source.

The PARA repo also documents a production-style web bundle flow through the Go server that serves the built app.

cd /Users/mlv/Desktop/MASTER/PARA
yarn
yarn build-web
cd bskyweb
go mod tidy
go build -v -tags timetzdata -o bskyweb ./cmd/bskyweb
./bskyweb serve --appview-host=http://localhost:2584

For the current shared demo host instead of the local AppView port, swap the final flag to --appview-host=https://appview.paramx.social.