Nusa Filament Laravel Package

Product Decisions This Supports

• Build vs. buy for Indonesian address/region handling: The package provides ready-made province, regency, district, and postal code data plus Filament v3 form/table helpers, so the team can avoid building and maintaining a custom regional dataset and cascading-select UI.
• Admin panel delivery speed: Filament v3 compatibility (^3.0) alongside Laravel 10/11/12 and PHP 8.1+ means it can be adopted in current and near-term Laravel admin stacks without version pinning workarounds.
• UX quality in address forms: The fix for postal code state reset when changing parent administrative regions directly improves checkout, registration, and customer-profile flows where users correct a province/regency/district.
• Performance of Filament tables and infolists: In-memory static caching in NusaOptions removes N+1 queries during table column and infolist rendering, lowering page latency and database load on admin screens that display many addresses.
• Scalable dependent dropdowns: Optimized query limits for child region dropdowns reduce payload and query cost when a parent region is selected, supporting smoother forms on large datasets.
• Roadmap input: The release signals active maintenance and Filament modernization. It supports prioritizing Indonesian localization work, address validation, and admin tooling now rather than deferring them.

When to Consider This Package

• Consider adopting when:

  • You are building Laravel 10/11/12 applications with Filament v3 admin panels that need Indonesian province, regency, district, and postal code inputs.
  • Your product has address capture, delivery, onboarding, or customer management flows specific to Indonesia.
  • You want cascading region dropdowns and postal code handling without owning the dataset maintenance and query optimization work.
  • You are standardizing admin forms and infolists and want to avoid N+1 queries from repeated region option lookups.

• Look elsewhere or proceed cautiously when:

  • You need real-time, authoritative regional boundary data with a guaranteed update SLA; verify the package’s data refresh process and legal/regulatory change cadence.
  • You are not using Filament, or are on Filament v1/v2, Laravel versions below 10, or PHP below 8.1.
  • Your address model depends on international regions beyond Indonesia.
  • You require enterprise support, long-term maintenance guarantees, or a multi-maintainer governance model; v1.0.0 is an initial stable release and should be validated for production risk tolerance.
  • You need advanced geospatial features, boundary polygons, or routing data rather than administrative names and postal codes.

How to Pitch It (Stakeholders)

For executives: This package gives us a production-ready Indonesian address and region capability for our Laravel/Filament admin tools. It reduces custom development and maintenance, improves address-form accuracy, and addresses performance issues that would otherwise slow admin screens. The v1.0.0 release confirms Filament v3 support and fixes a user-facing postal code bug, making it a credible candidate for current projects.

For engineering: Adopt for Laravel 10/11/12 + Filament v3 projects needing Indonesian administrative region data. The release adds Filament v3 support, fixes postal code reset behavior when parent regions change, adds static caching in NusaOptions to eliminate N+1 queries in table columns and infolists, and tightens child-region dropdown queries. Validate data freshness and maintenance ownership before relying on it as a system of record.