iLoader Next Development Status

What iLoader Next is, where it stands, and where to follow official updates.

Status: In development. There is currently no public stable release of iLoader Next.

What is iLoader Next?

iLoader Next is an active next-generation codebase for iLoader focused on a shared architecture for both web and desktop experiences. The public repository describes it as a combined web and desktop app for sideloading iOS apps.

Planned architecture

  • A unified frontend and desktop flow in one repo.
  • Shared Rust core logic for both desktop and web.
  • WASM bindings and a server component for the web side.
  • Developer workflow based on Bun + Rust toolchains.

Repository layout (public)

The public repository describes a multi-part structure intended to share logic across platforms:

  • frontend/ for React/Tauri frontend layers.
  • rust/iloader-core for shared core behavior.
  • rust/server for web-side proxy/API behavior.
  • rust/wasm for WebAssembly bindings to core logic.

Development commands (from public README)

If you want to evaluate the project locally, these are the commands documented in the repo:

Install dependencies

bun i && cd frontend && bun i && cd ..

Install wasm-pack

cargo install wasm-pack

Install Tauri CLI

cargo install tauri-cli

Start dev workflow

RUSTFLAGS="--cfg=web_sys_unstable_apis" bun dev

What “combined web + desktop” can unlock

  • Faster feature parity between desktop and web experiences.
  • Shared bug fixes in core logic instead of duplicate implementations.
  • A clearer path for browser-first onboarding and desktop power features.
  • Potentially more consistent error handling and diagnostics across platforms.

Pros and trade-offs (based on current public direction)

Potential pros

  • Single architecture can reduce long-term maintenance duplication.
  • Rust core + WASM may improve correctness and code reuse.
  • A unified repo can make cross-platform releases easier to coordinate.

Potential trade-offs

  • More moving parts (frontend + Rust + WASM + Tauri + server) increase setup complexity.
  • Toolchain requirements can be heavier for contributors.
  • A single repo can still become hard to manage if boundaries are not strict.

Predictions (clearly speculative)

These are forecasts, not official commitments:

  • iLoader Next may prioritize shared reliability features (errors/logging/diagnostics) early.
  • Web and desktop behavior is likely to align more closely over time if the shared core matures.
  • Contributor onboarding may improve once the “janky” dev workflow is stabilized in scripts/docs.

Official sources

For accurate progress updates, use these links first:

Community coverage exists, but treat it as secondary to the repo itself.

What should you use right now?

Use the current stable iLoader releases for production use and daily sideloading. This page is for tracking future development direction, not for installing iLoader Next today.

Download current iLoader Track iLoader Next