Lautta

I wanted to play games on the Mac I already owned. Getting one running could mean finding a compatible engine, preparing its files, changing settings and remembering the right way to launch it next time. Lautta puts that work behind a native Mac library.

I design and build the product: its identity, SwiftUI interface, website and the launch routes beneath them. The interface follows the state of the game. Missing files lead to setup; an installation in progress shows progress; a ready game offers Play. A compatibility label describes what has been tested, separately from whether the game is installed on this Mac.

That distinction matters. A game can be known to work and still need files or setup here. The player needs a useful next step at each point, with engine details available when they help diagnose a problem.

The technical route follows the game. Black Mesa runs through a locally built Wine runtime with the media components its menus and video need. Getting the game process to start was only part of the work; the route also had to survive returning through Lautta and loading a save.

Unemployment Simulator 2018 offered a different opportunity. Its Construct-based game could run in a native WebKit host. That avoided the broken web-view path inside Wine while keeping the game behind the same library and Play action.

The original 1997 Blade Runner from GOG uses its owned game data with a native ScummVM engine. I kept the downloaded package and existing saves untouched while testing that route. The public test note identifies the exact edition and separates the verified play session from the GOG import and distribution work still ahead.

These routes share a product interface while retaining the setup and test requirements of each game. Adding a game means making that particular route dependable.

A window opening is useful engineering progress. To earn “Tested with Lautta”, the record needs confirmed graphics, audio, controls, saving and loading after a fresh launch through Lautta. At the start of October, nine games had passed those checks on the test Mac, a MacBook Air M5 with 16 GB of memory.

The records retain the machine, route and game version where known. Steam build IDs let the app recognise that an update has changed the version under test. The earlier result stays in the record, but its confidence does not silently carry over to the new build.

The public library makes this evidence readable before someone tries a game. Partial tests have their own status, and the notes explain the gaps. A result on one Mac remains a result on that Mac; wider hardware coverage has to be earned through more testing.

Lautta is Finnish for ferry. The name gives the product a simple idea to build around: taking a game across to the Mac. The monochrome archipelago, ferry mark and restrained interface grew from that idea.

The website carries the landscape and introduces the games. Inside the app, the library, game artwork and current action do the work. The two surfaces share an identity while giving their space to different tasks: finding a game worth trying, then playing it.

The website, game notes and waitlist are live. The Mac app is in development. Local builds have been signed and notarised, and signed update verification is in place.

The next release work is to package the required engines, finish their distribution and licence review, and verify installation and updates on another Mac. There is no public installer yet. The next milestone is a complete build that can be installed and used without my development setup.