- What is Konekt AppShell and what does it include?
- Konekt AppShell is a modular Laravel application shell or boilerplate for building admin panels and business apps. It bundles authentication, users and customers, ACL wiring, settings, menus, widgets, localization, migrations, seeders, and Blade-based UI foundations. It is not a drop-in library you call from an existing app; it is an opinionated skeleton you build inside.
- Which Laravel and PHP versions does konekt/appshell support?
- The supported Laravel and PHP matrix should be verified against the package's composer.json and CI configuration rather than assumed. The technical assessment explicitly flags version compatibility as something to confirm for your target Laravel major. Check transitive dependency pins such as doctrine/dbal and Symfony components before committing.
- How do I install konekt/appshell in a new Laravel project?
- Adoption is mechanically straightforward: require the package with Composer, let service-provider discovery register it, publish migrations and configuration, and extend the supplied base User and Admin models. The realistic path is a greenfield install or a timeboxed spike on a throwaway branch. Pin exact versions and commit the lockfile, because upgrades should be planned work rather than routine composer update.
- Does konekt/appshell require konekt/concord and other Konekt packages?
- The package assumes its sibling Konekt ecosystem is present, including konekt/concord for modularity plus Konekt's ACL and address packages. The practical answer is to treat Concord as part of the architecture, even if composer.json does not hard-require every sibling. Verify module bootstrap order against Laravel package discovery, since providers loading after cached config is a common failure.
- Can I use konekt/appshell in an existing Laravel application?
- Retrofitting AppShell into an existing codebase is a re-platforming exercise, not a normal dependency install. It means replacing the user table, reconciling authentication guards, and rewriting policies around its conventions. For brownfield apps, the safer option is pattern harvesting: study its module structure and ACL schema, then implement equivalents natively.
- What ACL and permission model does konekt/appshell provide?
- AppShell ships ACL wiring built around Konekt's authorization package and opinionated user and admin models. The exact semantics, such as role-based versus permission-based checks and whether access is tenant-scoped, should be confirmed in the documentation for your pinned version. Do not assume compatibility with spatie/laravel-permission; pick one authorization model for the application.
- Can I use konekt/appshell with Filament, Jetstream, Breeze, or spatie/laravel-permission?
- It is likely to collide with those tools because AppShell dictates authentication scaffolding, the user model, and the admin UI chrome. Mixing it with Breeze, Jetstream, Filament, or a separate permission package creates two competing identity and authorization models. Choose AppShell's stack wholesale, or choose the other stack and borrow AppShell's patterns instead.
- Is konekt/appshell production-ready and actively maintained?
- The code is MIT licensed and forkable, but adoption signals are thin: low star count, no recorded public dependents, and maintenance that appears driven by the vendor's own products. That creates a bus factor of one and limited public tutorials or Stack Overflow coverage. Budget for forking to an internal namespace and owning upgrades rather than assuming community support.
- What test coverage and CI does konekt/appshell have for authentication and authorization?
- The technical assessment treats test coverage and the CI matrix for identity and authorization paths as an open question, not a documented strength. Inspect the repository's test suite and CI configuration before relying on it for login, role assignment, or tenant isolation. Write your own integration tests for those flows before feature work begins.
- How does konekt/appshell compare to Laravel Nova, Filament, or Jetstream?
- They solve different problems: AppShell is an application skeleton that defines users, ACL, migrations, and UI conventions, while Nova and Filament are admin-panel builders and Jetstream is authentication scaffolding. AppShell is a fit for a server-rendered, modular-monolith Laravel business app built greenfield by a team adopting Konekt conventions. It is a poor fit for API-first services or SPA, Inertia, or Livewire-first frontends that already have their own identity model.