Dynamic Fields Laravel Package

Product Decisions This Supports

• Admin UX and internal tooling investment: Supports decisions around making Laravel Nova admin screens more configurable without custom Vue/PHP work for every conditional or dynamic field requirement.
• Build vs. buy for Nova customizations: Gives the team a low-cost “trial before build” option when product/ops asks for dynamic field behavior in Nova resources. If it fits, it can reduce custom admin development; if not, the spike informs a small internal implementation.
• Roadmap sequencing for internal operations: Helps prioritize admin configurability features—conditional fields, dynamic form behavior, role/state-driven inputs—by testing whether a small package can satisfy near-term needs.
• Use-case validation: Useful for prototypes or low-risk internal admin workflows where product wants to validate whether dynamic fields improve data entry quality, reduce form errors, or simplify ops workflows before committing to a larger form-builder initiative.
• Vendor/fork decision: With very low adoption signals, it supports an explicit decision to either vendor/fork the package for critical internal use or avoid making it a dependency in customer-facing or long-lived systems.

When to Consider This Package

• You are already standardized on Laravel Nova and need lightweight dynamic/conditional field behavior in Nova resources.
• The need is internal/admin-facing, low-to-medium criticality, and can tolerate a small, low-adoption dependency after code review.
• Engineering can pin the version, review the source, and fork/vendor if the package becomes important.
• A short spike can confirm the package’s actual feature set, Nova version compatibility, maintenance status, and security posture.
• Look elsewhere if you need a full form builder, public-facing dynamic forms, complex workflow rules, guaranteed support/SLA, high-scale reliability, or if you are not using Nova.
• Treat stars/dependents as a risk signal: 2 stars and 0 dependents means limited community validation, so avoid making it a core platform dependency without an exit plan.

How to Pitch It (Stakeholders)

Executive summary: This is a small Laravel Nova add-on that may let us deliver dynamic admin form behavior faster and cheaper than custom development. It is worth a limited technical spike for internal admin use cases, but its low adoption means we should not treat it as strategic infrastructure. Approve only as a time-boxed evaluation or a vendored/forked dependency with clear ownership.

Engineering summary: Evaluate nurmuhammet/dynamic-fields against our Nova version and exact dynamic-field requirements. Review the source, test edge cases, pin the version, and document fallback/fork strategy. If it saves meaningful custom Nova work for internal tools, adopt narrowly; otherwise build the minimal behavior we need or choose a better-supported alternative.