Square Enix’ new smartphone titles fail to offset weak performance from existing | Pocket Gamer.biz
Square Enix’ latest financials show that their mobile segment’s sales have continued to decline compared to the previous year, despite the launch of a major new title.
Their Q1 2024 financials saw an increase of net sales by 14.4% ($601.6m) but a drop in operating income of -78.5% ($2.7m) year on year, however, Square Enix predicts a rise in sales by 24% year-on-year for the whole 2024 period ($2.5bn).
Dragon Quest Champions, which launched in June, had high hopes pinned on it, specifically to boost the performance of the company’s mobile segment. Its lukewarm performance can perhaps be partially attributed to Square Enix shuttering a number of mobile titles in 2023, such as Bravely Default: Brilliant Lights and Echoes of Mana, which may have drawn away the audience for these titles who didn’t return for DQ Champions.
As noted specifically in their report, “In the Games for Smart Devices/PC Browser sub-segment, ‘DRAGON QUEST CHAMPIONS’ was launched in June, but the sub-segment’s net sales declined compared to the same period of the previous fiscal year because of weak performances from existing titles.”
Mobile millstone?
Although Square Enix is far from being in dire straits, it would seem that they are struggling to break through in mobile. As previously stated, the drop in sales could be partially attributed to their closure of other titles during the earlier parts of 2023, however Square Enix are quick to note that the poor performance of other existing titles contributed to the low performance. However, the failure of Dragon Quest Champions to significantly impact their mobile segment, despite accruing $100m within its first week, will still sting.
It raises the question of whether Square Enix’s mobile strategy needs a revamp, as the company boasts many potent IPs and well-known titles that could easily be translated into (and often have been) mobile titles. Their focus on the notoriously sticky blockchain market has failed to materialise much in the way of performance and while the company continues to enjoy broadly positive critical and audience reception for their recent mainline Final Fantasy XIV, sales are now slowing. All of which points to a confused approach at a time when gaming remains on the up on nearly all platforms.
window.fbAsyncInit = function() {
// init the FB JS SDK FB.init( appId : 250161755076617, // App ID //channelUrl : '//'+window.location.hostname+'/channel.php', // Path to your Channel File status : true, // check login status cookie : true, // enable cookies to allow the server to access the session xfbml : true // parse XFBML );
FB._PG = url: "/useractions/loginfb/", response: "allowed",
// Common handler to fetch FB details and reload the page process: function(me) $.post( FB._PG.url, username: me.username, uname: me.name, uid: me.id, uimg: 'https://graph.facebook.com/' + me.id + '/picture?type=large' ) .done(function(xml) if ( $("status", xml).text() == FB._PG.response ) window.location.reload(); else alert('Error: Something bad just happened. Our tech department has been notified. Please try again later.');
) .fail(function(xml)
alert("Error: something wasn't right there, please try again.");
); ,
// Used by event subscriptions to handle the response handleResponse: function(response) if (response.authResponse) FB.api('/me', function(me) if (me.name) FB._PG.process(me); );
,
post: function(text, image) $("#fb-image").attr("src"); FB.ui( method: 'feed', display: 'popup', link: 'https://www.pocketgamer.biz/news/82125/square-enix-new-smartphone-titles-fail-to-offset-weak-performance-from-existing-catalogue/', description: text, picture: image );
;
FB.Event.subscribe('auth.statusChange', FB._PG.handleResponse);
FB.Event.subscribe('edge.create', function(response) $.post('/ajax/social-links/', site: 'facebook' ); ); };
(function(d, s, id) var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "http://connect.facebook.net/en_US/all.js"; fjs.parentNode.insertBefore(js, fjs); (document, 'script', 'facebook-jssdk'));