Strapi

Public discussion around Strapi over the past four weeks has been dominated overwhelmingly by frustration, with bugs and reliability concerns accounting for the vast majority of mentions. Commenters surfaced issues ranging from session-timeout behavior that silently discards unsaved work to multi-tab logout cascades, wildcard filter escaping problems, and GraphQL ordering inconsistencies. The sheer volume of bug reports relative to praise signals that a large portion of the active community is encountering friction in day-to-day use rather than celebrating capabilities.

Sentiment tracked at its weakest in the opening weeks of the window, sliding to a low point in mid-May before a modest recovery around the third and fourth weeks of May. That brief uptick did not hold, and scores dipped again in early June before a sharp climb in the most recent period, driven by a notable surge in mention volume. Whether that final jump reflects renewed optimism or simply a louder wave of activity is unclear from the data, but the overall trajectory suggests the product has spent most of the window in a low-confidence zone with only intermittent stabilization.

Praise, while sparse, clustered around feature quality and ease of use. A small number of commenters acknowledged the product positively for its integration story and collaborative potential, and a few mentions expressed appreciation for ongoing maintenance. However, these voices were significantly outnumbered by those cataloguing problems.

Division in opinion was most apparent around the maturity and stability of the platform. Some discussion suggested active community engagement through feature requests and RFCs, pointing to a segment of users invested in the product's direction. Others appeared more worn down, with reliability complaints framing their frustration as compounding rather than isolated. The gap between the engaged-builder tone of some threads and the bug-report exhaustion of others created a split in the overall texture of discussion.