Optimized 3D Characters for Mobile Games: Low-Poly, PBR, Rigging

Creating Efficient 3D Characters for Mobile Games

You're developing a mobile RPG. The main character looks great in Blender, but on a Samsung Galaxy A32 you get 20 FPS. Balancing visuals and performance is the key challenge in mobile 3D graphics. A low-poly model is not about poor quality—it is about smart resource distribution. Our experience includes over 50 characters for 15 games across different genres. We know how to avoid such issues.

Why Polygon Budget Matters

Every extra triangle increases vertex processing load and memory bandwidth usage. On mobile devices with limited thermal headroom, exceeding the budget causes throttling and FPS drops. We ensure the model fits within given limits without losing visual quality. Target budgets for different genres:

These are triangles (tris), not polygons. In Unity and Godot, counters show tris. Blender by default shows faces—multiply by ~2 for triangulated meshes.

LOD (Level of Detail) is mandatory for characters that can be far from the camera. LOD0 (full), LOD1 (50–60% polycount), LOD2 (25%). Unity's LODGroup component switches automatically based on distance. The draw call savings are significant in scenes with 10+ characters.

How We Create 3D Characters for Mobile Games

The process starts with analyzing project requirements. We determine the style, genre, and target devices. Then we develop a technical specification that fixes the polygon budget, texture format, and rig settings. This is critical for subsequent optimization. For example, for hyper-casual titles, the main character can have only 500–1500 triangles, while for midcore RPGs, up to 8000. Choosing incorrectly at the start leads to rework and extra costs. Our engineers set the right parameters upfront, saving your project budget.

Rig and Skinning

Humanoid rig. We use Unity Animator with Avatar for humanoid characters. This allows using motion capture and Mecanim transitions. The number of bones is 20–40 for a mobile character. More means higher CPU load for skinning.

Generic rig. For creatures, vehicles, non-standard shapes. Fewer constraints on bone hierarchy. BlendTree in Animator ensures smooth transitions.

Skinning quality. In Unity's Quality Settings > Skin Weights for mobile, we use 2 Bones instead of 4 Bones. The deformation difference is minimal, and the CPU savings are noticeable with 20+ characters on screen.

Blend shapes (morph targets) for facial expressions. Each blend shape is an extra vertex pass. On mobile, we limit to 5–10 key expressions for the main character.

How to Choose Between Humanoid and Generic Rig

If the character is humanoid and you need ready-made animations, choose humanoid. For unique creatures (dragons, robots), generic gives more control over the skeleton. In most mobile projects, humanoid is more efficient due to animation reuse and lower development cost.

Textures and Materials

Texel density—pixel density per unit surface area—must be consistent across all characters in the scene. A character with a 4K texture next to an NPC at 256px looks unprofessional.

Standard PBR textures: Albedo (Base Color), Metallic/Roughness (or Specular), Normal Map, Emission (optional). On mobile, Normal Map is often left only for the main hero.

Texture atlasing. Multiple characters on one atlas = one Material = one Draw Call. Especially important for battle scenes with identical enemies. In Unity, GPU Instancing + shared Material allows drawing 100 identical enemies in one draw call.

Compression: ASTC 6x6 for iOS, ETC2 for Android. For Albedo — ASTC 6x6 (lossy but acceptable). Normal Map — ASTC 4x4 (needs precision for lighting).

From practice: a midcore RPG on Unity URP. A scene with 15 enemies gave 200+ draw calls, 25 FPS on iPhone 11. After implementing GPU Instancing + shared Material + LOD1 for enemies beyond 10 meters — draw calls dropped to 45, stable 60 FPS. Only pipeline settings changed, models untouched. This shows how proper texture and material optimization saves resources and budget.

Comparison of URP and Built-in

URP is the standard for new mobile projects. It is up to 2x faster than Built-in on mobile devices due to optimized rendering. Stylized shaders (cel shading, toon) are popular in mobile games and are implemented via Shader Graph without coding: Ramp Texture for lighting + Fresnel for rim light = cartoon look.

Character Creation Process

1. Blocking — base shapes from primitives.
2. Detailing — anatomy refinement.
3. Retopology — clean topology for animation. Manual for deformable areas (joints, face).
4. UV unwrapping — optimal use of texture space.
5. Normal baking — transferring details from high-poly to low-poly.
6. Texturing in Substance Painter (Albedo, Normal, Metallic/Roughness).
7. Rig and skinning — humanoid or generic rig, weight painting.
8. Test in engine — check animation and shader on target device.
9. Optimization — profiling, LOD and draw call tuning.

What's Included in the Work

• 3D modeling with polygon budget compliance
• UV unwrapping with optimal texture space usage
• Baking high-poly details → low-poly
• Texturing (Albedo, Normal, Metallic/Roughness)
• Rig and skinning for humanoid or generic rig
• LOD0 + LOD1 + LOD2
• Export to FBX/glTF with settings for Unity / Godot
• In-engine test with animation and shader verification

Timelines and Budget

Creating one casual-level character (1500–4000 tri, basic texture set, humanoid rig) takes 2–4 weeks. A midcore hero with full texture map, blend shapes, and LOD takes 4–8 weeks. Serial production of similar NPCs is faster due to base mesh reuse. The cost typically ranges from $500 for a hyper-casual character to $3000 for a midcore hero. Proper optimization can reduce overall production expenses by up to 40%. For a hyper-casual game, outsourcing a main character costs around $500, while a midcore hero may cost $3000. Contact us to discuss your project. We'll evaluate the task and propose the optimal solution that fits your budget and timeline. Your game will get a hero that won't let you down under load. Request a consultation on character optimization.

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.