Sonata Permission Bundle Laravel Package

Product Decisions This Supports

• Feature prioritization: The multiple_choice option (checkbox or radio) directly enables survey, quiz, onboarding, application, and preference-capture features without custom field work. This lowers the cost of shipping any roadmap item that depends on structured user input.
• Build vs. buy: If the team is considering a custom form/field system, this package is a credible “buy/assemble” option for Laravel apps that need configurable choice inputs. It reduces time-to-market for a common, deceptively expensive UI/data concern.
• Use cases unlocked: Customer feedback forms, NPS/CSAT, lead qualification, internal approval requests, event registration preferences, consent and policy acknowledgements, lightweight quizzes, and admin-configurable settings.
• Scope control: Because the package adds choice-field support as a small, focused feature, PMs can treat it as an enabler rather than a platform bet — useful when the product needs to validate demand before investing in a heavier form builder.
• Roadmap signal: The 1.0.x line is still adding core field types. Plan around it for straightforward forms, but avoid committing to complex conditional logic or advanced form workflows until the package’s scope is clearer.

When to Consider This Package

Consider adoption when:

• You are building on Laravel/PHP and need configurable multiple-choice inputs (radio for single-select, checkbox for multi-select) with minimal custom code.
• The product needs many small forms or admin-defined fields where rebuilding field rendering, validation, and persistence in-house would slow delivery.
• Your requirements are moderate: standard validation, storage, and display of choice-based answers, not complex branching, scoring, or enterprise form governance.
• You want a low-ceremony dependency that fits existing Laravel conventions and can be evaluated quickly.
• You are validating a feature — surveys, onboarding, preference capture — and want to avoid over-investing before demand is proven.

Look elsewhere or plan additional build work when:

• You need advanced conditional logic, multi-page branching, calculated fields, or complex scoring.
• You require enterprise form operations: versioning, approval workflows, granular permissions, audit trails, or deep analytics.
• The product depends on rich field types beyond basic choice inputs — file uploads, signatures, repeatable groups, matrix questions — and the package’s roadmap is unproven.
• You need long-term API stability guarantees; a 1.0.x package adding field types is still maturing.
• The choice field behavior must be highly customized (searchable multi-select, async option loading, dependent option sets), which may exceed what a lightweight package should own.

How to Pitch It (Stakeholders)

For executives: This package gives us a faster, lower-risk path to shipping forms that capture structured user input — surveys, onboarding questions, preference selection, consent flows. The new multiple_choice support covers one of the most common input patterns (radio and checkbox groups), which means we can validate several product ideas without building a custom form system. It is a tactical enabler, not a strategic platform commitment: adopt it where requirements are standard, and revisit if we need complex branching, analytics, or enterprise controls.

For engineering: The 1.0.2 release adds a focused multiple_choice option supporting checkbox and radio rendering. It is a small surface-area addition that fits Laravel conventions and should be low-risk to evaluate. Recommend a time-boxed spike: wire it into one real form, confirm validation/storage behavior and extensibility, then decide whether it becomes the default for simple choice-based forms or remains a narrow tool. Avoid betting complex workflows on it until the package demonstrates broader field-type and logic support.