- Is MobileKit v4 a Composer package I can require, or a starter kit?
- MobileKit v4 is a starter kit and application scaffold, not a library you composer require. You clone or fork the repository and the codebase becomes yours on day one, with upstream serving as a reference rather than a source of updates. Treat adoption as a fork-and-own decision and socialise that with engineering leadership before spending evaluation time.
- How do I install MobileKit v4 on a new Laravel project?
- The documented entry point is the repository itself, so expect a clone or create-project style setup rather than a package install command. Check the README for the exact bootstrap steps, environment configuration, and NativePHP tooling requirements before you start. If no install command is published, budget time for a manual hardening pass covering dependencies, CI, signing, and secrets management.
- Does MobileKit v4 work with Laravel 12, or is it Laravel 13 only?
- It is built on Laravel 13.x and Filament 4.x, both of which are bleeding-edge majors relative to the wider ecosystem. There is no documented downgrade or backport path, so compatibility with Laravel 11 or 12 should be verified by testing, not assumed. Ask what the upgrade path looks like when Laravel 14 lands, because a scaffold pinned to newest majors inherits plugin incompatibilities quickly.
- What is Filament 4 used for in MobileKit v4?
- Filament 4 provides the admin and back-office panel that sits alongside the Laravel application layer. For teams already familiar with Filament, the mental model transfers cleanly: one language, one ORM, one authorization story. Confirm whether the shipped panel is multi-tenant and whether an API layer such as Sanctum or Passport is included, or whether same-origin webview calls are assumed.
- Is NativePHP in MobileKit v4 truly native, and which device APIs are covered?
- NativePHP wraps the Laravel runtime in a native shell for iOS and Android, so the UI is largely web-driven rather than truly native. It suits form, workflow, and data-capture apps well, but heavy animation, offline-first sync, and deep device-API work are exactly where webview and native-bridge architectures accrue hidden cost. Identify which NativePHP plugins are wired in and which device capabilities are not covered before committing.
- Can I ship a MobileKit v4 app to the App Store and Play Store?
- Shipping is feasible in principle, but NativePHP mobile build tooling, plugin coverage, and bridge semantics are the least proven part of the stack. Plan for code signing, store review, and any capability that needs a custom native plugin, which may fall outside your team's skillset. Ask who has actually shipped this stack to production stores and what review cost they incurred.
- Does MobileKit v4 include tests, CI, and static analysis?
- Test coverage, CI configuration, and a static analysis baseline are not established from the public signals around the repository, so verify them directly before committing. If quality gates are thin, add an explicit hardening sprint before the first feature: dependency audit, CI pipeline, signing setup, and secrets management. The cost of that sprint belongs in your evaluation, not in your first release.
- Is MobileKit v4 actively maintained, and what is the bus factor?
- Adoption is very low, with roughly 14 stars, which means little community, few tutorials, and effectively no peer review of the code. It is maintained by a single author, so bus factor and supply-chain risk are real and cannot be contracted around. Recent releases help, but recent is not the same as stable; treat upstream as read-only and plan to own your fork.
- What license does MobileKit v4 use, and does NativePHP cost extra?
- Confirm the repository license first, since a starter kit becomes your code and license terms follow it. NativePHP itself has licensing implications to check, including paid tiers or per-app fees that are separate from the starter kit. Those costs should be modelled per app and per store listing before you commit.
- What are the best alternatives to MobileKit v4 for a Laravel mobile app?
- If you already have a mobile team, a Laravel API with a React Native or Flutter client is more conventional, and the kit's value shrinks to a NativePHP bootstrap reference you can read in an afternoon. For admin-only needs, standard Laravel starter kits plus Filament cover the back office without the native shell. If you adopt MobileKit, go greenfield and extract its patterns rather than grafting it onto an existing production app.