A few words about Pocket Trains

David and Ian’s projects have a strange magic. They are not friendly to the casual user. At the start of almost any of their games, the user is faced with a bunch of screens, micromanagement, related to them, and not the most understandable tutorial.

At the same time, if you do not spare five minutes and figure out what NimbleBit offers, the player risks being “stuck” in the project for a long time. The same is the case with Pocket Trains.

The key word in the game is logistics. The user decides which cargo is more profitable to carry to a particular city, opens new paths and new trains. Time and fuel are spent on transporting goods, but gold is added. Gold is spent on laying paths and buying currency. The currency allows you to instantly replenish the fuel supply, fulfill orders faster, and also purchase trains. The more trains, the more goods can be transported in a certain period of time and, accordingly, earn more. 

Due to the need to constantly manage supplies, decide who will go where, the user is forced to constantly return to the project. In addition, each time you return to the game, Pocket Trains notifies you how much the user has earned since the last call. In fact, this is a kind of encouragement, a prize that encourages the player to tap on the application icon as often as possible (those who have released games on mobile markets should be familiar with this feeling when, for the first time after the release, every five minutes you go to the admin panel showing downloads).

A great way to stimulate user retention, which Nimblebit used back in Tiny Towers.  

Another indisputable advantage of Pocket Trains is its intimacy and meditativeness. This is not enough for many mobile projects today. The user should want to return to the project, he should be comfortable in the game. The Marches have achieved this. The only question now is whether they will be able to make good money on it.