Laravel Review Rateable Laravel Package

Product Decisions This Supports

• Feature prioritization: Enables criterion-level review features such as rating distributions for overall, quality, or other keys, making it easier to justify roadmap items like aspect-based review filtering, per-criterion dashboards, and targeted quality insights.
• Build vs. buy: Reduces the case for custom rating aggregation logic. v2.3.0 adds injectable criterion querying through CriterionRatingContract while preserving existing all-criteria methods and requiring no database migration, lowering adoption cost.
• Use cases: Product marketplaces, ecommerce review modules, SaaS feedback forms, vendor scorecards, and any Laravel app needing approved-review lists, rating stats, and distributions segmented by rating criterion and department.
• Roadmap enablers: Supports follow-on features such as “top-rated by quality,” per-criterion moderation queues, department-specific reporting, and unapproved-review workflows without reworking the data model.
• Operational decisions: Teams can choose default approved reviews and the default department, query across departments with null, or include unapproved reviews where appropriate—useful for moderation and internal analytics.

When to Consider This Package

• Adopt when: You are building on Laravel/PHP, need polymorphic ratings/reviews, want multiple rating criteria, require approved-review filtering, or need department-aware reporting. v2.3.0 is especially relevant if you need rating counts, stats, or review lists for a specific criterion rather than aggregating all criteria together.
• Strong fit when: You want to avoid a schema migration for criterion querying, need backward-compatible behavior with existing rating query methods, or prefer an injectable contract for testability and service substitution.
• Look elsewhere when: You are not on Laravel/PHP, need advanced NLP/sentiment analysis, require a fully hosted review platform, or have rating aggregation needs that are too bespoke for a package’s conventions. Also reconsider if department and approval semantics do not match your domain model.

How to Pitch It (Stakeholders)

• For executives: v2.3.0 unlocks criterion-level review insights—such as quality-specific ratings and distributions—without a database migration. It reduces custom development for review analytics, speeds delivery of customer-facing review filters and internal dashboards, and keeps existing behavior stable.
• For engineering: The release adds ratingCountsForKey, ratingStatsForKey, and getReviewsByRatingForKey, plus an injectable CriterionRatingContract. Existing all-criteria queries remain unchanged, defaults favor approved reviews in the default department, and teams can opt into other departments, cross-department counts, or unapproved reviews. No migration means low rollout risk.
• For product: Prioritize aspect-based review experiences and per-criterion reporting. Validate whether your domain needs department segmentation and approval workflows; if so, this release provides a low-risk path to ship those capabilities faster.