01 / BEFORE YOU BEGIN
What you'll need.
On the sending side
- A Windows 10/11 x64 PC and Pyli for Windows.
- Internet access, a working HTTPS route and enough free disk space for your retained APKs.
- A single, installable
.apk for each build. An .aab or split APK collection cannot be installed through Pyli. - Keep the PC awake, online and Pyli running while phones connect.
On the receiving side
- Android 8.0 or later and the Pyli companion app.
- Network permission to reach the sender's PC. A private Tailscale setup requires Tailscale on the phone too.
- Space for the download and Android's installation work.
- The phone owner's approval for each installation. Delivered apps must support the phone's Android version and processor.
No Android SDK, Java, Node.js or wireless debugging is needed for everyday use. The Windows installer bundles its runtime; the installed agent helper uses Windows PowerShell. An organization's device policy may restrict installation or scripts.
APK size: Pyli's self-hosted Windows/Android delivery path supports up to 1 GiB (1,073,741,824 bytes) per APK. Leave additional storage available. An external relay or tunnel provider may impose a smaller request, storage or timeout limit; check with its operator.
A phone-only tester does not need Windows or their own server. Normal Pyli use requires no Craigish account and no AI subscription. Windows and Android are the supported companion apps; a Mac sender is a future possibility.
02 / WATCH THE HANDOFF
See the whole journey.
▷Video coming soonFrom invitation to installation.
A YouTube walkthrough will appear here when its approved link is available. It will show pairing, downloading a demo build, Android's installation permission and the confirmed result.
The written steps below are complete without the video. No YouTube player or third-party request loads on this page today.
03 / THE SENDING SIDE
Install Pyli on Windows.
- Get the authorized Windows package. Use the official Store listing when it becomes public, or the exact package supplied for your invited test. Avoid third-party download sites.
- Install the app. For an invited desktop-installer build, run Setup, choose your folder and optional Desktop/Start Menu shortcuts, then finish. Store packages use Windows' normal installation flow and may offer different choices. Review any Windows security message; do not disable protections to force installation.
- Open Pyli - Phone Portal. In Settings, select Host my own server on this computer for the normal self-hosted setup. The app creates its protected server credential itself; no credential file is needed.
- Prepare the connection below. Save its complete HTTPS address in Settings, then choose Start server. Check the status line before creating invitations.
Updating Windows Pyli
Use the same distribution channel and app identity. For a desktop-installer update, first choose Quit from Pyli's tray menu, then run the supplied update package. Closing the window ordinarily leaves Pyli in the tray. Preserve the existing profile and data; do not uninstall first or erase settings to solve an update problem. Store installations follow their Store update flow.
Using someone else's relay instead?
Select Connect to an external relay only if a Pyli server operator supplied its HTTPS address and a developer credential file. Save the address before importing that file; changing the relay address clears the old credential. Tailscale supplies connectivity, not a Pyli developer credential.
04 / THE ADDRESS PHONES USE
Connect to the PC.
The server address is the secure address where phones reach Pyli on your Windows PC. It is not the phone's IP address, a Tailscale account, or merely a 100.x address with https:// added.
EXAMPLE ONLY · USE YOUR OWN SERVER'S ADDRESShttps://your-pc.your-tailnet.ts.net:8443
- Phone listener:
http://127.0.0.1:47842. Your HTTPS connection forwards to this listener. - Administration/uploads:
127.0.0.1:47841. Keep this local to the PC. Never forward this port or share it with phones.
If the tunnel runs on the same PC, leave Let phones on this network reach the listener off. The tunnel reaches the loopback listener without opening it on all network interfaces.
Choose a private connection such as Tailscale Serve below, or ask a knowledgeable operator to provide a trusted HTTPS tunnel to the phone listener. Public tunnels have different exposure and provider limits; Pyli does not automatically configure one. A VPN such as ZeroTier alone does not create a trusted HTTPS endpoint.
05 / PRIVATE NETWORK OPTION
Tailscale, step by step.
Check whether Tailscale is already installed and connected before installing it again. Tailscale downloads ↗ · Machines in your admin console ↗
- Connect both devices. Run Tailscale on the PC and Android phone. Sign in to a network that permits the phone to reach the PC. Being on the same Wi-Fi does not establish tailnet membership or access.
- Find the PC, not the phone. In Tailscale's Machines list, open the Windows PC and find its full DNS name ending in
.ts.net. Configure Serve next; a name alone does not create the route. - Inspect existing routes first. Open Windows Terminal with PowerShell (administrator access may be required), and run this complete command:
& "C:\Program Files\Tailscale\tailscale.exe" serve status
Keep routes belonging to other apps. Do not use serve reset. - Use an unused HTTPS port. If 8443 has no existing route, run:
& "C:\Program Files\Tailscale\tailscale.exe" serve --bg --https=8443 http://127.0.0.1:47842
If 8443 is already occupied, choose another unused HTTPS port, such as 8444, and carry that port through the remaining steps. - If Serve needs enablement, open its printed link in your browser. The terminal may wait while you sign in and enable HTTPS for your own network. Leave optional Tailscale Funnel unchecked for this private setup. HTTPS certificates disclose the device DNS name in public certificate-transparency logs; read Tailscale's notice before approving. If needed, use the admin console's DNS/HTTPS certificates controls. Official HTTPS instructions ↗
- Check the route and copy its real URL. Run
serve status again. Copy the complete HTTPS URL associated with 127.0.0.1:47842, including :8443 (or the port you selected). - Finish in Pyli. Paste it into the HTTPS server/phone connection address field in Settings. Choose Save settings, then Start server. The status should show the phone listener and Phones pair at with your full HTTPS address.
Browser links and commands are different. Open https://… links in a browser. Paste only the command lines into PowerShell. A documentation link is not the personal enablement link printed by Tailscale.
Tailscale Serve is private to permitted devices in your tailnet. Funnel is a separate public-access feature and is unnecessary for this path. Keep Tailscale connected on the phone when pairing, refreshing or downloading. Official Serve guide ↗ · Command reference ↗
06 / THE RECEIVING SIDE
Install Pyli on Android.
- Use your authorized Pyli installation link. Public availability is still coming soon. Invited Google Play testers must join the specified tester group, accept the test with the same Google account used in Play, and install from the supplied Play link. Group membership alone is not installation.
- If your invitation provides a Pyli APK instead, verify its source. Download it from the sender's trusted location and open it. Android may ask for installation permission for the browser or file app opening that APK. Read its prompts and approve only software you trust.
- Open Pyli. Connect Tailscale first if your sender uses a private Tailscale route. Have the sender's fresh invitation ready.
No USB connection, developer options or wireless debugging is required for normal Pyli delivery. Those are development tools, not part of this setup.
Permissions you may see
- Install unknown apps: Android grants this separately to each source app. Permission for a browser or My Files to install Pyli does not give Pyli permission to install delivered apps. When you choose a trusted build in Pyli, Android can open the source-permission screen for Pyli. Return and retry installation after your decision.
- Notifications: delivered-build alerts are optional and off by default. Enable them in Pyli if you want them, then approve Android's notification request if shown. Android's app/channel settings can also mute alerts. Alerts do not download or install apps automatically.
- System protection: Play Protect, Samsung Auto Blocker or an organization's device policy can block installation. Read the actual result. Pyli cannot override it; ask the developer for a supported trusted build when uncertain.
07 / INVITATION ONLY
Pair each phone once.
- On Windows: open Devices and create an invitation. Use a separate invitation for each phone. Each eight-character code is single-use and expires after 15 minutes.
- On Android: scan/open the invitation through Pyli's supported invitation flow, or copy the complete Phones pair at HTTPS address and invitation code into Pyli. QR scanning may depend on the phone's camera or scanner app.
- Review the address and phone name. Confirm the address belongs to the sender. Use the friendly name you want the sender to see; the device model is a fallback. The saved pairing name appears in the Windows recipient list; renaming is optional.
- Choose Review and pair. Confirm the details. Once paired, the phone appears under Devices on Windows and can receive selected builds without a new invitation each time.
If the code expires or has already been used, request a new one. A valid code cannot grant Tailscale access or fix an unreachable server. Never post real codes or invitation links publicly.
Changing the server's public address can leave existing phones using the old address; arrange a fresh invitation/re-pairing as needed. Revoke access blocks future server access; it does not uninstall apps already on the phone.
08 / THE FIRST DELIVERY
Send. Review. Install.
On Windows
- Open Build inbox. Choose or drop a single APK (up to 1 GiB on the self-hosted path). Check its package name, version and size.
- Add a useful title and release notes. Select exactly the paired recipients who should receive it.
- Choose Queue build. After successful queueing, the compose area clears for the next send. Manage the existing delivery from Recent builds, including its per-phone receipts.
On Android
- Open Pyli and choose Refresh inbox if needed. Open the delivered build and read its notes.
- Choose Download. Pyli writes the APK to private storage and checks its size and SHA-256 before offering installation. Keep the connection available; interrupted downloads may offer a resume/retry action.
- Choose Install with Android. Review any Pyli confirmation, then Android's installation prompt. If Android asks for Pyli's source permission, make your choice, return to Pyli and retry.
- Stay with the active build and complete any pending system prompt. The build card reports Android's result; approving a download alone is not approval to install.
QueuedAvailable for the selected phone
DownloadedReceived and verified
InstalledConfirmed by Android
Queued does not mean installed. Foreground inbox checks and Android's scheduled background work are not instant push delivery. Background restrictions, server availability and the phone's network can delay checks; opening Pyli and refreshing is the clearest way to check.
Pyli verifies transfer integrity. Android checks package compatibility and signing during installation. Only deliver APKs you are entitled to share and trust.
09 / THE NEXT BUILD, WITHOUT THE CLUTTER
Reinstall & tidy up.
Windows · server management
- Archive / Restore: withdraw or restore a build for future phone downloads while retaining its payload and history. Archived files still take disk space.
- Delete: remove its server payload and future download availability. Audit metadata/receipts remain. This cannot remove copies already downloaded or installed.
- Default retention is ten ready builds with a 30-day expiry; older or expired payloads may become unavailable. Check your relay's settings.
Android · this phone only
- Reinstall: the action at the bottom of an app card reuses a verified cached APK, or offers another download if the server still has it. Android approval is still required.
- Delete downloaded file: removes the cached APK, not the installed app or its saved progress.
- Archive on this phone / Restore to inbox: organize local cards without changing the sender's server.
- ✕ / hidden history: tidy a local list; use the available hidden/archive view to restore items. Active work can prevent hiding, and a new delivery may make an item visible again.
Keep your progress. A normal update needs the same package identity, a compatible signing certificate and a permitted version. If Android reports INSTALL_FAILED_UPDATE_INCOMPATIBLE or signatures do not match, stop and contact the developer. Do not uninstall or clear app data as a default fix. A Play-installed app may require an update signed by Google Play's distribution key; a locally signed APK can conflict even when its name matches.
Reinstalling an APK is not a backup or a guarantee of saved-game compatibility. The delivered app controls its own data and migrations.
10 / A HELPING HAND, IF YOU WANT ONE
Have AI? Bring your helper.
Windows Pyli includes optional offline setup handoff files and a bundled Pyli skill for compatible agents. Use the Have AI/setup-help entry to choose guidance for OpenAI/ChatGPT/Codex, Claude, Devin or another capable tool. Copy the instructions or provide the file using that tool's normal attachment/skill workflow.
A local agent with your permission may inspect installed Pyli/Tailscale status and guide setup. A chat-only assistant can explain the same steps but cannot operate your PC without a supported connection. The kit is documentation, not a built-in model; no AI account is required.
Ask the helper to inspect the existing installation and routes first, preserve pairing/history, explain any requested system permissions and wait for your approval where needed. Keep tokens, credential files, live invitations and private APKs out of public chats. Never ask an agent to bypass Android's install confirmation.
11 / WHEN SOMETHING GETS IN THE WAY
Find the next step.
“Unable to resolve host” or no address found
Check the complete PC DNS name and HTTPS port. For a .ts.net route, confirm Tailscale is connected on both devices, the phone has access to the sender's tailnet and MagicDNS is working. The phone's own IP address is not the relay address. Refresh or retry only after connectivity is restored.
Tailscale is running, but pairing still fails
Running Tailscale does not itself configure Serve. Check serve status, the HTTPS enablement step, the selected port and its target 127.0.0.1:47842. In Pyli, Save settings before Start server. Check the PC is awake and the phone is permitted to reach it. A code cannot override a network access rule.
PowerShell says the link is not a command
Open HTTPS links in a browser. In PowerShell use only the complete command lines in the Tailscale section. If tailscale is not on PATH, use its full installed path as shown.
Invitation expired, invalid or already used
Create a fresh invitation on the same server, use it on one phone within 15 minutes, and review the complete address before pairing. Do not reuse another phone's code.
The build is queued but absent on the phone
Confirm that exact phone was selected as a recipient and remains paired. Check the server is running and reachable, then open Pyli on the phone and Refresh inbox. Optional notifications do not guarantee immediate background delivery.
Download interrupted, storage error or size mismatch
Restore the connection and use the card's resume/retry control. Free sufficient space for the APK plus installation work. A provider's smaller upload cap can still reject a large APK; ask the relay operator. A size/SHA-256 mismatch must be resolved by a fresh valid download or corrected sender build, not by skipping verification.
Android is waiting for permission or installation approval
Return to the active build and inspect Android's prompt. Search Android Settings for Install unknown apps and check Pyli specifically. Permission for the browser that installed Pyli is separate. A pending install is not a confirmed success.
Play Protect, Samsung Auto Blocker or a managed phone blocks it
Read the exact message and ask the developer for guidance on a trusted supported build. An offered Play Protect scan differs from a harmful-app warning; do not disable Play Protect or ignore a harmful-app result. Device restrictions may prevent sideloading even when Pyli came from Play. Google's Play Protect help ↗ · Samsung Auto Blocker help ↗
Signatures conflict, a newer version exists, or the APK is incompatible
Preserve the installed app and data. Send the developer the exact Android result. They may need the original signing identity, a newer version or the Google-signed distribution APK. For other incompatibility errors, check Android version and processor support. Pyli cannot re-sign another app or bypass a downgrade restriction.
Reinstall is unavailable or a build is gone
A deleted cache requires a new download. Server deletion, expiry, recipient changes or revoked access can make that impossible; ask the sender to deliver a current compatible build. Local cleanup does not restore a removed server payload.
I'm using the optional reference testing environment
Follow the private instructions supplied with your invited test. That isolated environment serves a harmless demonstration, may be unavailable while its host is offline and can recycle inactive sessions. Its login is separate from normal self-hosted Pyli. Never publish its credentials; if your session expired, use the supplied test instructions or contact support. You do not need to create your own Windows server for that demonstration.
12 / YOUR DEVICES, YOUR CONTROL
Privacy & support.
Normal Pyli delivery runs through the server you or your operator control. The Pyli privacy policy covers both companion apps and the optional reference testing environment. Existing Android and Windows policy addresses remain available.
For help, email craigish.com@gmail.com with your Pyli version, Windows/Android version, the step that failed and the exact error. Remove credentials, live invitation codes and private addresses from screenshots before sending. For a delivered app's own bug or saved progress, contact that app's developer.
Back to the beginning ↑