📆Native UI
Platform-native dialogs and pickers that match iOS and Android design guidelines
What You'll Learn
Why Native UI Matters
Tutorial Roadmap
Key Use Cases
Prerequisites
Last updated
Platform-native dialogs and pickers that match iOS and Android design guidelines
Essential Kit's Native UI feature provides platform-native alert dialogs and date/time pickers without maintaining platform-specific code. This tutorial walks you through creating professional UI components that feel native to each platform.
Using PlayMaker? See the PlayMaker guide: PlayMaker.
Looking for a working reference? Open the demo scene at Assets/Plugins/VoxelBusters/EssentialKit/Examples/Scenes/NativeUIDemo.unity and the companion script at Assets/Plugins/VoxelBusters/EssentialKit/Examples/Scripts/NativeUIDemo.cs to see the full API in action.
Create alert dialogs with multiple buttons and text input fields
Build date and time pickers for user input collection
Handle dialog callbacks and user interactions properly
Design platform-appropriate UI flows
Business impact: Professional dialogs increase user trust and engagement
UX impact: Native components feel familiar and match platform conventions
Technical impact: No custom native UI code needed across iOS and Android
Setup - Enable Native UI feature
Usage - Alert dialogs, date pickers, and input handling
Testing - Validate on both platforms
FAQ - Troubleshoot common issues
Show confirmation dialogs for important actions (purchases, deletions, exits)
Collect user input through native text fields and dialogs
Let users pick dates for scheduling (tournaments, reminders, events)
Display time pickers for notification settings and alarm features
Create multi-button dialogs for complex decision flows
Unity project with Essential Kit v3 installed and Native UI feature included
iOS or Android build targets for testing native appearances
Understanding of callback patterns for async dialog interactions
Last updated