shpapps

Lab · Tool

Blip Foundry

Design the small sounds and haptics behind taps, toggles and rewards. Hear them, feel them on a phone or watch them on the timeline, then take them home: a WAV, an AHAP file for Core Haptics, Kotlin for Android, Web Audio code. Everything is made in this browser.

  • Nine starting sounds
  • Haptic timeline
  • WAV and AHAP
  • Swift, Kotlin, Web Audio
  • Runs in your browser

Try them

Today

Playground

Coins: 120

Level 3

Sound, touch and motion, on the same beat.

Tap a tile to play it. It also opens in the editor.

Coin

Haptic event

Haptic event type

Drag an event along the lane to move it and up or down to change its intensity; click the empty lane to add a tap.

Tone
Wave
Envelope
Texture

Take it home

The sound as a file, the haptics for each platform, and the synth itself as code.

blip-coin.wav

Field notes

What the platforms say about feedback

  1. Clear, not buzzy

    Android sorts haptics into clear ones, crisp like a physical button, and buzzy ones that leave a tingle after they stop. Its advice for touch feedback: given the choice of a buzzy haptic or none, choose none. Short taps are what Blip Foundry starts you with.

    Source: Android, haptics design principles

  2. System feedback for system moments

    For standard actions Android points apps to HapticFeedbackConstants, so effects stay consistent and the platform can fall back on simpler phones: CONFIRM and REJECT since Android 11, TOGGLE_ON and TOGGLE_OFF since Android 14. iOS has UINotificationFeedbackGenerator for success, warning and error. Keep custom patterns for the moments that are yours, like a reward.

    Sources: Android, haptics design principles · HapticFeedbackConstants · UINotificationFeedbackGenerator

  3. Sound, touch and motion on one beat

    Apple asks for haptics that complement what people see and hear, matched to the intensity and sharpness of the animation they go with. Android recommends designing the three together and warns that a haptic out of sync with the visuals and audio can feel unsettling. An AHAP file can carry the sound itself, so both start together.

    Sources: Apple HIG, Playing haptics · Android, haptics design principles

  4. Less is more, and optional

    Apple: avoid overusing haptics, since one that feels right once can grow tiresome, and let people turn them off. Android: keep effects on frequent events like scrolling very subtle, and make important ones, like submitting a form, stronger than a toggle.

    Sources: Apple HIG, Playing haptics · Android, haptics design principles

  5. Respect the silent switch

    On iOS, interface sounds suit the ambient audio session category: it is for apps that still work with the sound off, mixes with other apps' audio, and is silenced by the Silent switch and by locking the screen.

    Source: Apple, AVAudioSession.Category.ambient

  6. Each platform counts time its own way

    An AHAP event's Time is seconds from the start of the pattern. In an Android composition a primitive's delay counts from the end of the previous one, and gaps under about 50 ms are hard to feel apart; the Kotlin here subtracts the real lengths on Android 12 and later. On the web, navigator.vibrate() is on and off only, needs a user gesture, and Safari and Firefox do not vibrate.

    Sources: Apple, AHAP files · Android, custom haptic effects · MDN, Navigator.vibrate()

Built with plain HTML, CSS and JavaScript. Each sound is rendered once with Web Audio's OfflineAudioContext: what you hear is the same audio as the WAV, and the Web Audio tab exports the very function that made it. No libraries, no uploads; your edits stay in this browser.