Web app in. Real phone app out.
Your web app,
repacked as a real app.
RepackOS wraps the web app you already built in a native Android and iPhone shell, then gives it the powers a website can't have.
Android and iPhone shells working Background GPS next
Websites keep asking. Apps remember.
- iPhone Safari asks for the camera again and again
- No background GPS once the screen locks
- Lives behind an address bar, easy to lose
- Camera permission asked once, then remembered
- Native modules for what the web can't do
- Its own icon, full screen, no browser bar
Three steps. No rewrite.
- 01
Keep the web app you have
React, Next.js, anything that runs in a browser. RepackOS loads it as-is, so you keep shipping updates from your own server.
- 02
Describe it in one small file
Name, app ID, start page, which sites are allowed inside, and which phone powers it needs.
{ "name": "PileProfit", "appId": "com.yourcompany.app", "startUrl": "https://your-web-app.com/app/", "allowedHosts": ["your-web-app.com"], "backgroundColor": "#121417", "permissions": ["camera"] } - 03
Build and install
One command builds the Android app, another sends the iPhone app to your phone through TestFlight, privately. Nothing reaches the public App Store unless you choose to publish.
./gradlew assembleDebug -Papp=pileprofit
What the shell adds
Camera, asked once
The phone asks one time. After that your own pages get the camera with no popup, even after the app is closed.
Locked to your site
Only your allowed hosts open inside the app. Every other link opens in the phone's browser.
Feels native
Full screen, back button, file picker for uploads, login kept between launches, friendly offline screen.
JavaScript bridge
window.NativeApp lets your page check camera status, open the app's settings and more.
iPhone shell
Same config, native Swift shell, delivered privately through TestFlight.
Background GPS
Tracks field teams with the screen off, logs offline and uploads when the signal returns.