Skip to capabilities

Mobile games · Native iOS · Interactive systems

PIPIT!

A small game with a lot happening underneath.

PIPIT! is a portrait arcade game about dodging birds, surviving boss encounters, and coming back for one more run. Its technical story combines native iOS game engineering, touch interaction, reusable game data, progression, and a clear separation between gameplay rules and visual effects.

PIPIT app iconPIPIT!Dodge the flock.Available on the
App Store
PIPIT App Store screenshot: Dodge the flock, showing the game on an iPhonePIPIT App Store screenshot showing a boss encounter
Under the surface

A connected system.
Every layer has a job.

01Touch input
02Gameplay rules
03Visual + audio response
04Saved progression
Native iOS implementation
Swift · SpriteKit · SwiftUI

The game scene, rendering, and app-level interface.

Game systems
State machines · Collision envelopes · Wave scheduling

Movement, bird behavior, fair dodges, and difficulty.

Content & progression
Typed JSON catalogs · Local saved progress

Stages, worlds, bird definitions, stars, and unlocks.

Distribution & discovery
App Store presentation · Product & press pages

Gameplay screenshots, download paths, and support information.

What the technology makes possible.

PIPIT! / Engineering capabilities
01

Native iOS game engineering

The iOS implementation brings a real game loop into a mobile application.

Technical detail
  • SpriteKit scenes and nodes written in Swift.
  • SwiftUI hosts the game and app interface.
  • Scene layers separate the playfield, actors, effects, and HUD.
  • Portrait presentation fits short, touch-driven play sessions.

A mobile experience can respond continuously rather than behave like a collection of web forms.

02

Gameplay and visual effects stay separate

A successful dodge becomes a visual payoff without turning into a second obstacle.

Technical detail
  • Bird state machines distinguish active threats from resolved effects.
  • Collision and near-miss envelopes define the interaction rules.
  • Bonk resolution runs outside the active dodge system.
  • Deterministic fairness checks cover hits, near misses, and clean passes.

The game can look lively while keeping the player’s rules understandable and fair.

03

Data-driven content and difficulty

Stages and birds are described as reusable content rather than one-off screens.

Technical detail
  • JSON catalogs decode into typed stage, world, and bird definitions.
  • Wave scheduling and stage configuration control pacing.
  • Playfield templates and projection keep gameplay coordinates consistent.
  • Per-bird tuning supports different movement patterns and collision behavior.

New content can build on a shared system instead of requiring the game to be rewritten for every level.

04

Progression on the device

Stars, scores, discoveries, and unlocks give each run a place in a longer journey.

Technical detail
  • Saved stage records include best scores, stars, and completion state.
  • World and boss access follow explicit progression rules.
  • Bird discoveries and near-miss achievements feed collection progress.
  • The published game can be played without creating an account.

A lightweight experience can still remember achievement and give players a reason to return.

05

Touch, feedback, and presentation

The interaction combines quick movement with readable visual and sensory feedback.

Technical detail
  • Swipe-based dodging and visible threat patterns.
  • Sprites, layered environments, and immediate score and near-miss feedback.
  • Audio, haptics, and settings are part of the published game experience.
  • The game’s own App Store screenshots show play, bosses, and progression.

Good mobile engineering connects what a person does to a response they can immediately understand.

06

A product beyond the game scene

The project also includes the public surfaces needed to explain and support a released game.

Technical detail
  • App Store game presentation and a direct download destination.
  • A public product page with platform-specific download paths.
  • Press assets, gameplay screenshots, privacy information, and a feedback form.
  • Store presentation uses actual gameplay rather than a generic brand illustration.

Shipping an app includes its discovery, communication, and support experience.

Search & distribution

Built to be found.
Clear when it is.

Discoverability needs its own engineering: the right public information, the right metadata, and clear paths into the experience.

App Store presentation

A clear game identity, action category, subtitle, and gameplay screenshots communicate the experience.

Gameplay proof

Screenshots from the current listing show dodging and boss encounters, not just character artwork.

Public product pages

Download, press, privacy, and feedback pages give the game a useful presence beyond the store.

Clear next actions

Visitors can understand the game, open its store listing, or find support without guesswork.

For your next idea

Different project.
New possibilities.

Native mobile products, touch-driven experiences, casual games, gamified tools, simulation interfaces, and reusable interactive content systems.

Talk through your project

Build on these capabilities