Weave Code
Platform Ui Laravel Package
enjin/platform-ui
Enjin Platform UI is a Laravel package that provides ready-made Blade components, layouts, and frontend assets for building consistent Enjin Platform interfaces. It helps teams ship admin screens, NFT workflows, and blockchain tooling faster with reusable UI patterns and less custom CSS.
A package for adding a user interface to the Enjin Platform.
Frequently asked questions about Platform Ui
- What is enjin/platform-ui used for?
- It is the presentation layer for the Enjin Platform, providing ready-made Blade components, layouts, and frontend assets for admin screens, NFT workflows, wallets, minting, and transfers. It sits on top of enjin/platform-api and platform-core, so it is not a standalone UI kit. Use it when you are adopting or already operating the Enjin Platform and want a consistent operator console.
- How do I install enjin/platform-ui in a Laravel app?
- Install it with Composer require enjin/platform-ui. The service provider is auto-discovered; publish the config and frontend assets, then mount the routes behind a prefix in your Laravel app. You need a compatible enjin/platform-api instance already running, because the UI is the presentation layer, not a standalone console.
- Is enjin/platform-ui a standalone UI library?
- No. It is the presentation layer of the Enjin Platform and expects enjin/platform-api, platform-core, and the Enjin daemon or beam infrastructure. Installing it by itself yields little beyond published assets and routes. The real decision is whether you are adopting the entire Enjin Platform or adding a console to an instance you already run.
- Which Laravel and PHP versions does enjin/platform-ui support?
- The package follows Laravel and PHP 8.x conventions and is aimed at Laravel 10 and 11 estates, but the exact constraints live in its composer.json. Check and pin the published PHP, Laravel, database, and Node requirements before adoption. Do not let Composer float these versions, especially if your estate includes older Laravel releases.
- What infrastructure does the Enjin Platform UI require?
- You need a reachable Platform API, the database that API owns, queue and cache workers, and a daemon holding signing keys with fuel. A non-production testnet stack is the sane starting point. Without those services the UI renders but cannot perform meaningful NFT, wallet, minting, or transfer work.
- How is authentication handled in enjin/platform-ui?
- The auth model is a key pre-adoption question: confirm whether it uses Laravel session, Sanctum, or wallet signature auth, and whether it ships authorization gates or assumes the host app's. Audit every route the package registers for middleware coverage. Put the console behind SSO or VPN and treat auth misconfiguration as an on-chain risk.
- Can I use enjin/platform-ui without enjin/platform-api?
- No. It depends on enjin/platform-api for GraphQL data and on platform-core plus the daemon for signing and chain operations. Without a compatible API and daemon, the UI has nothing to talk to. The hard dependencies are environmental, so feasibility ranges from an afternoon to a multi-week infrastructure project.
- Is the Enjin Platform UI safe for production admin use?
- Treat it as high-risk until you add controls. The console can mint, transfer, and manage keys, so a UI bug or auth mistake can cause irreversible on-chain loss. Validate a testnet mint and transfer via API first, then run a read-only UI smoke test and audit routes. Mount it behind SSO or VPN with approval workflows, audit logging, and a rollback and key-rotation drill before production.
- How do I handle version compatibility between platform-ui, platform-api, and platform-core?
- This package is version-locked to the platform-api GraphQL schema and will break on drift, often with a UI that renders but errors opaquely. Pin platform-ui, platform-api, and platform-core to mutually tested tags and confirm the schema hash the UI expects matches the API you run. Add compatibility checks to CI rather than letting Composer resolve versions.
- Is enjin/platform-ui actively maintained, and what are the alternatives?
- It is vendor-maintained, but in the evaluation it had zero stars, zero score, and zero dependents, so there is no external validation or community integration history. You would be the de facto first adopter and are betting on the vendor's continued releases. Alternatives are building your own Laravel UI against the Platform API GraphQL schema, or using any hosted Enjin-managed portal if one exists.
Weaver
How can I help you explore Laravel packages today?