Snapchat Web Lenses open another door for PlayCanvas games

A web game can now become a Snapchat Lens. PlayCanvas announced support for Snapchat Web Lenses in October, adding another destination for developers who already build games with browser technology. The workflow starts with a web build and ends with a ZIP uploaded through My Lenses, without requiring a Lens Studio project.

We have already seen platform-specific opportunities through the YouTube Playables challenge and Deploy to Wavedash challenge. Snapchat adds another set of constraints to consider when deciding where a small game belongs.

Start with the phone

Snap’s overview describes Web Lenses as self-contained web apps running inside Snapchat. Games are the initial focus, the feature is in beta, and PlayCanvas is used throughout the documentation, although other web frameworks can be used.

The intended format is a portrait mobile game. That matters before you choose a camera angle, draw a menu, or decide how many buttons the player needs. A desktop prototype with a miniature keyboard diagram is not automatically ready for someone holding a phone in one hand.

Try making the first useful action visible on the opening screen. A player should be able to touch something and understand the result without hunting for instructions. For a score game, that could mean putting the first target within reach immediately. For a puzzle, begin with a move that demonstrates the rule before introducing a difficult board.

The announcement includes Bloom, Ball Smasher, Snake Showdown, and Bitmoji Ski as early examples. They provide different starting points for thinking about touch input, short sessions, and reasons to return. Their presence on the platform does not mean every web game needs to imitate their genres.

Package a complete game

The platform requirements currently specify a compressed ZIP of no more than 8 MB, with an index.html file no larger than 1 MB at its root. Asset references must be relative. These are beta requirements, so check the current documentation again before submitting.

The runtime cannot use the network, camera, microphone, or motion sensors. Persistent storage, leaderboards, and Bitmoji support come through the Web Lens API; ordinary browser storage starts empty on each launch. That makes external asset downloads and a conventional online multiplayer backend poor assumptions for a port.

Make an inventory of what your game loads. Fonts, music, textures, analytics, and remote configuration can be easy to overlook when everything works on your development machine. Then test the actual packaged output. A successful local development server is only one stage of getting a playable build into someone else’s hands.

Developers who enjoyed the resourcefulness behind js13kGames 2026’s 317 entries will recognise the value of knowing what each asset contributes. The limits are very different here, but measuring the final package is still more useful than guessing.

Make platform features earn their place

A leaderboard is useful when the score describes something players want to improve. Before adding one, decide whether a run rewards accuracy, speed, survival, or a combination. Show the result clearly and make another attempt easy to start. Otherwise the integration can be technically complete while adding little to the game.

Saved progress needs the same thought. Decide which information must survive a session and which can safely reset. A best score, an unlocked stage, and an unfinished run have different consequences when loading fails or the player leaves abruptly.

For a practical design reference, our Little Ski tutorial coverage looks at a deliberately small game intended for devices from phones to laptops. Its scope is a useful starting point for a port experiment, regardless of which engine you use.

Try one small release first

Choose a project with a short path from launch to play, then check touch controls, screen edges, audio activation, pausing, and restarting on a real phone. Keep a note of every platform-specific change so later updates do not accidentally undo it.

Follow the Web Lenses documentation for the current submission process. A finished small release will tell you much more about this destination than a large port waiting for its final integration work.