Designing Mobile Game Mechanics

Every second mobile project fails due to boring mechanics: the player leaves by the third minute, day one retention drops below 20%. The cause is a poorly designed feedback loop. We design the core loop so that every tap delivers a dose of dopamine and the meta loop makes players return daily. For example, for a hyper-casual slicer, day one retention grew from 28% to 41% after adding difficulty escalation through an AnimationCurve. Time saved on balancing by externalizing parameters into ScriptableObject: up to 30%. We guarantee retention increase to 41% based on practice. Contact us for a project analysis.

How core loop differs from meta loop

Core loop — an action repeated every 30–120 seconds. In Tower Defense: place a tower → wave of enemies → result → resources → next wave. In an idle game: tap → coins → upgrade → more coins per second → tap less. The loop must be understandable without a tutorial and be satisfying on its own. Meta loop — progress over several sessions: unlocking new towers, characters, levels. Meta loop retains the player between sessions — gives a reason to return tomorrow. A common mistake: designing meta loop before core loop. If base gameplay is boring, no progression saves retention. In a mobile game, core loop should be 3 times shorter than on PC due to attention span differences.

How mobile constraints change mechanics

The mobile screen dictates mechanics. A click at 100 ms on PC — a tap at 200 ms on a touchscreen. A mouse with pixel precision — a finger 10 dp wide. These are not drawbacks — they are design parameters. As Game Design Workshop states, mobile mechanic design must account for these delays.

Works well on mobile:

• Swipe mechanics (Tinder-style, match-3, slice)
• Tap and hold (charging, aiming)
• Time management (Cooking Dash) — limited time on a small screen creates tension
• Pinch to scale (strategies, city simulators)
• Gyroscope (mazes, racing games) — via Input.gyro in Unity

Works poorly:

• Precise aiming (mouse shooters)
• Simultaneous control of multiple objects
• Fast reactions (<100 ms) — physiological limit of touchscreens

Designing mechanics with monetization in mind

Monetization should not break the core loop. Energy system (lives in Candy Crush) — artificial throttling of the core loop. Works in terms of IAP but damages user experience. Alternative: cosmetic monetization (skins, effects) — does not limit gameplay, preserves player experience. If the project uses ad monetization (rewarded video via Unity Ads, AdMob, IronSource), mechanics are designed with "decision moments" — points where the player willingly watches an ad: continue a level after losing, double the reward. Forced ads destroy flow. Reducing balancing costs through parameterization: up to 40%.

How to design a mechanic: 5 steps

1. Define the genre and target audience. For hyper-casual, core loop should be 5–30 seconds; for RPG, 10–30 minutes.
2. Draw a state machine of input event → state → effect. Ensure all loops close.
3. Externalize numeric parameters (speed, damage, timers) into ScriptableObject (Unity) or JSON config — this speeds up balancing 3 times compared to hardcoding.
4. Build a prototype by day five and test retention on 20 subjects.
5. Iterate: after mechanic tweaks, day one retention increases on average 10–15%.

// Example state machine for a slicer (pseudocode)
states: IDLE, SWIPING, CUTTING, COMBO, EXPLOSION
IDLE -> SWIPING (on touch start)
SWIPING -> CUTTING (if collider hit)
CUTTING -> IDLE (if combo timer > threshold)
CUTTING -> COMBO (if combo multiplier active)
IDLE -> EXPLOSION (on bomb touch) -> GAME_OVER

Documenting mechanics

Each mechanic is documented in a GDD with:

• Description of player action
• Expected feedback (what they see/hear)
• Parameters (numbers, timers, multipliers) — in format for ScriptableObject
• Edge cases: what happens at 0 HP, when inventory is full, on connection loss

Parameter constants in code are the enemy of balance. All numeric parameters are externalized to ScriptableObject or JSON config. Game designer can tweak balance without a developer.

Typical mechanics by mobile genre

Typical mistakes in mechanic design

What is included in the work

• Genre and target audience analysis
• Core loop design considering mobile input
• Description of all mechanics with balancing parameters
• State machine diagrams for key systems
• Documentation in GDD format (mechanics sections)
• Monetization recommendations without breaking gameplay
• Prototype verification of key mechanic (by agreement)

Timeline

3–5 working days for mechanic design of hyper-casual or casual project. For midcore RPG / strategy with several interconnected systems — 5–10 days. Price is calculated individually after concept analysis.

Contact us for a project evaluation. Order end-to-end mechanic design and get a prototype for retention testing within a week.

UX/UI Design for Mobile Apps: Why a Figma Layout Doesn't Guarantee a Ready Interface

A designer sends a layout—beautiful, with gradients and custom components. The developer opens it and realizes: the button is 36pt, the tap target is 20pt. On an iPhone SE, it's physically impossible to press with a thumb. The bottom sheet covers content when the keyboard appears. Navigation is built against the native iOS model. Apple will reject the app, or users will leave within a week—depending on how lucky you get with the review.

We have been designing mobile UX/UI for over 5 years and have seen hundreds of such situations. During this time, we have designed and helped launch 30+ mobile apps—from fintech products to social networks. You don't need to guess whether the design will pass App Review or Google Play—we embed platform requirements from the first screen. We'll assess your project in one day, contact us.

Mobile UX/UI is not an adaptation of web design. It is a separate discipline with specific platform constraints: safe area, touch gestures, UIViewController lifecycle, Activity state management.

Why Can't You Ignore Human Interface Guidelines and Material Design 3?

Apple HIG and Google Material Design 3 are not aesthetic recommendations. They are documented user expectations formed by years of using system applications. Expectations confirmed by user experience research on mobile platforms (User experience design).

HIG defines: minimum tap target 44×44 pt, safe area insets for notch and Dynamic Island, standard gestures (swipe back on iOS, back gesture on Android 10+). Ignoring safe area is a common mistake. safeAreaLayoutGuide in UIKit and safeAreaPadding in SwiftUI exist precisely for this. A designer who doesn't set safe area margins in Figma guarantees a bug during development.

Material Design 3 introduced Dynamic Color—the color scheme is generated from the user's wallpaper via MaterialTheme.colorScheme in Jetpack Compose. An app that ignores dynamic colors on Android 12+ looks out of place. This is not critical for niche products but is noticeable in mass-market apps.

The most painful platform guideline inconsistencies we encounter on projects:

• Custom navigation on top of system navigation. iOS users expect swipe back from any point on the left edge of the screen. A custom NavigationController without interactive gesture breaks this. Android users expect the system back button—a custom back button in the left corner does not fully replace it.
• Modal windows instead of navigation push. Bottom sheets are appropriate for actions, not for navigating content.
• Missing haptic feedback. UIImpactFeedbackGenerator on iOS is not decoration but part of the interface response. Buttons, swipes, and confirmation actions without tactile feedback feel broken.

Table: Comparison of iOS and Android UX/UI Requirements

How to Get the Most Out of Figma?

The Figma Variables API has changed the workflow. Design tokens—colors, typography, radii, spacing—are stored as variables and exported directly to code via figma-tokens or style-dictionary. This eliminates manual value transfer and desynchronization between design and implementation. Practice shows: Figma Variables speeds up asset handoff to development by 2–3 times compared to static frames, and using design tokens reduces code transfer errors by 60%.

Auto Layout with wrap and spacing between elements allows building components that behave like flex containers. A developer opens a component and sees not a static artifact but a description of behavior at different content sizes.

Component Properties—variants, boolean toggles, instance swaps—enable building a full design system right in Figma. A button with 4 states (default, hover, pressed, disabled), 3 sizes, and 2 icon variants is one component, not 24 frames.

Figma Prototype with Variables allows creating an interactive prototype with real state: showing how the screen changes with different variable values. This is no longer just a "clickable layout" but a full UX testing tool.

How to Benefit from Prototyping and UX Testing Before Development?

The most expensive mistake in a mobile product is to develop a feature, release it, and discover that users don't understand how it works. A Figma prototype at the testing stage costs zero development hours. Redoing a finished screen costs days. Testing a prototype before development begins reduces the number of fixes by 80%.

For usability testing, we use Maze (task testing on a prototype—the user goes through a scenario, we get heatmaps and mis-click rates) or direct sessions via UserTesting. Key metrics are task completion rate and time on task, not "like/dislike."

A/B testing on mobile is harder than on web: the App Store doesn't allow UI changes without an app update. Therefore, it's important to test hypotheses on a prototype before release, not through production experiments. According to research, fixing a bug found on a prototype costs 10 times less than after production release. And average task completion time increases by 40% after proper UX optimization during prototyping.

Why Are Animations Critical for Interface Perception?

Animations in mobile apps are feedback. An element doesn't appear instantly—it transitions to the desired state over 200–350 ms. This gives the brain context to understand what happened.

• iOS: withAnimation in SwiftUI, UIViewPropertyAnimator in UIKit for interactive animations with interruption capabilities. Spring animations with dampingRatio are the basis of most Apple system transitions.
• Android: AnimatedVisibility, animateContentSize, Crossfade in Compose. MotionLayout for complex scenes with multiple transformations.
• Flutter: AnimationController + Tween, Hero animations between screens, Lottie for After Effects exports. Lottie is especially effective for onboarding illustrations and empty states.

The key constraint is 16 ms per frame (60 fps) or 8 ms (120 fps on ProMotion devices). Animations must run on the GPU via CALayer/RenderThread, not on the CPU via layoutSubviews. Profiling via Core Animation instrument in Xcode is a mandatory step before releasing animated screens.

Why Is Accessibility Not an Optional Feature?

VoiceOver on iOS and TalkBack on Android are used by up to 15% of users—this statistic is confirmed by accessibility research described in Accessibility (Wikipedia). In absolute numbers for a large app, this is thousands of people. Additionally, App Store rejections due to accessibility occur, though rarely.

Minimum checklist:

• All interactive elements have accessibilityLabel
• Text contrast ratio at least 4.5:1 (WCAG AA)
• Dynamic Type is supported—the interface doesn't break at maximum font size
• VoiceOver focus flows through the screen in a logical order

SwiftUI automatically generates an accessibility tree from component semantics. UIKit requires manual setup of accessibilityTraits, accessibilityHint, and grouping via shouldGroupAccessibilityChildren.

What Does the Work Include?

The UX/UI design deliverables include:

What Is the Process and Timeline?

Design goes through stages: research and competitive analysis → user flows and wireframes → design system → UI layouts → prototype → testing → handoff to development.

Timeline estimates:

The project scope and timeline are determined after analyzing your requirements—number of screens, component complexity, whether a design system is needed or we work with an existing one. Get a consultation for your project—contact us for a preliminary assessment. Order a complete mobile app design—we'll assess your project in one day and propose the optimal work scope.