Revolut

Discussion around Revolut over the past four weeks was dominated by frustration, with bugs and reliability issues accounting for the large majority of complaint-themed mentions. Commenters described crashes tied to specific app versions, authentication failures in integration contexts, and payee data being lost during bank imports. The technical specificity of many complaints suggested that a portion of the discussion was coming from developers or technically engaged users rather than casual consumers, which may have sharpened the critical tone even at low mention volumes.

The score trajectory tells a volatile story rather than a clean directional one. Sentiment climbed meaningfully in the first half of May, reaching a relative high around mid-May before collapsing sharply in the week of May 11th. It then recovered across the following two weeks before falling back again in early June. This oscillation makes the overall picture feel unstable rather than improving or worsening in any sustained way, and the low mention counts at several data points mean individual negative posts likely had outsized weight on any given week.

Praise was sparse but present. Several mentions cited favorable comparisons to competitors and pointed to specific features approvingly, and ease of use drew at least one positive note. These positive signals were notably outnumbered, however, and did not appear to generate the same depth of conversation that bug reports did.

Opinion was most divided on the integration front. Some discussion suggested Revolut was being adopted or considered as a component in developer workflows and third-party tooling, with commenters treating it as a capable platform. But other mentions in this same space highlighted authentication conflicts and missing data fields, creating a split between those who saw integration potential and those who had run into concrete technical walls trying to act on it.