- What is johntrickett86/tall-mobile?
- johntrickett86/tall-mobile is a mobile-first TALL preset for Laravel projects using Tailwind CSS, Alpine.js, and Livewire. It helps developers build responsive, app-like interfaces and streamline mobile layouts and interactions. It is distributed as a Composer package.
- How do I install johntrickett86/tall-mobile in a Laravel app?
- Install the package with Composer using composer require johntrickett86/tall-mobile, then apply the preset according to the package README. Confirm the package's Laravel, Livewire, Alpine.js, and Tailwind constraints before installing. Run your normal Laravel asset and view build steps after applying the preset.
- Which Laravel versions and TALL stack versions does tall-mobile support?
- The provided context does not list an exact Laravel version matrix. Check the package's composer.json for Laravel, Livewire, Alpine.js, and Tailwind constraints before installing. Confirm compatibility with your application's current versions rather than assuming support for every release.
- Is tall-mobile a full Laravel starter kit or just a preset?
- It is described as a mobile-first TALL preset rather than a complete application starter kit. It provides mobile-oriented tooling and layout or component conventions that you apply to a Laravel project. Treat it as scaffolding for the front end and Livewire interaction layer, not as a full application.
- What changed in tall-mobile v1.0.1?
- The v1.0.1 release note describes moving the modal directory into components. That is usually low risk when the move is internal to the package. It can break consumers that reference old modal view paths, Blade component names, or published modal overrides.
- Is tall-mobile v1.0.1 a breaking change for modal views?
- Potentially yes. If your app directly includes the old modal path, uses component names derived from it, or has published modal views, update those references or relocate overrides to the new components location. If the package provides compatibility aliases or the move is internal-only, the upgrade may still be a simple dependency bump.
- How do I upgrade safely from tall-mobile v1.0.0 to v1.0.1?
- Treat v1.0.1 as potentially breaking until verified. Grep your application for old modal view references, component tags, includes, and published overrides, then review the package diff and changelog. Run staging tests that open and close modals and render any overrides, and keep a rollback pin to v1.0.0 if rendering fails.
- Can I publish or override tall-mobile Blade views?
- If the package exposes publishable Blade views, you can publish and customize them in your Laravel app; otherwise use supported view namespaces for overrides. After v1.0.1, verify whether modal overrides need to move under the components directory. Check the package's publish tags and documentation before relying on overrides.
- What are alternatives to tall-mobile for Laravel TALL projects?
- Laravel Breeze with Livewire, Laravel Jetstream, and other TALL presets are common alternatives. Compare mobile-first layout defaults, modal organization, Blade override support, and upgrade history. tall-mobile is specifically aimed at app-like mobile interfaces, so choose based on how closely its preset structure matches your project.
- Is tall-mobile suitable for production and what maintenance issues should I expect?
- It can be suitable for production if it uses standard Blade and Livewire conventions and your tests cover modal rendering, layouts, and overrides. Maintenance is low when the v1.0.1 modal move is internal, but customized or published modal views may require extra upgrade work. No direct scaling impact is expected because the change is file organization rather than runtime capacity.