Skip to content

Repository files navigation

GameLovers Mobile Services

Unity 6 services for local notifications, native UI, haptics, permissions, App Tracking Transparency, deep links, gestures, and mobile build tooling.

UnityLicense: MITVersion

Scope

Use Mobile Services to isolate platform-specific behavior behind Unity-friendly APIs. It provides local notifications, not remote push delivery; it also does not provide connectivity or store fallback services. The package is pipeline-neutral.

Unity compatibility

ItemCurrent policy
Minimum Unity version6000.0
Reference streams6000.0.x, 6000.3.x, 6000.5.x
Reference editors6000.0.81f1, 6000.3.21f1, 6000.5.7f1 (primary)
Render pipelinePipeline-neutral
Validation statusCompatibility target; do not treat a stream as validated until the repository matrix records it.
PlatformIntended behavior
iOS / AndroidNative services and build-time configuration
EditorPlatform simulator and no-op/mock backends where applicable
StandaloneLimited fallback behavior; haptics reports unsupported
WebGLNot supported

Install and configure native projects

{
"dependencies": {
"com.gamelovers.mobileservices": "https://github.com/CoderGamester/Unity-MobileServices.git#1.2.0"
}
}

Before using permissions, notifications, ATT, or native UI:

  1. Create and commit the Mobile Services settings/config asset.
  2. Fill in every required usage description and capability for the platforms you ship.
  3. Decide whether the package or your project owns generated native files.
  4. Validate an iOS and Android build on physical devices.

Without persisted configuration, the build postprocessor has no configuration to apply; it cannot infer missing privacy keys or capabilities.

First success

Create owners during application startup and dispose them during teardown. Scheduling a notification transfers it to the operating system; disposing its service does not cancel already-scheduled OS notifications.

usingSystem;usingGameLovers.MobileServices.Haptics;usingGameLovers.MobileServices.Notifications;usingUnity.Notifications.Android;varhaptics=newHapticsService();haptics.Play(HapticPreset.Selection);varnotifications=newMobileNotificationService(newGameNotificationChannel("default","Default","General notifications"));// Keep this owner and call Dispose when your application service is torn down.IDisposableownedNotifications=notifications;

Use the specific subsystem namespaces—Notifications, Haptics, NativeUi, and Device—rather than assuming one umbrella import exposes every type.

Services

AreaProvides
Native UIDismissible or blocking alerts, action sheets, toasts, review requests, and sharing
NotificationsLocal notification channels, scheduling, and management
HapticsPresets, custom output, and bounded loops
DevicePermissions, ATT, deep links, safe-area and device helpers
GesturesGesture controller for explicit gesture input ownership
Editor toolingDevice Simulator integration and build helpers

Runtime alert calls render an interactive platform-shaped mock in the Game view even when the Device Simulator window is closed. Prefer ShowAlertPopUpAsync for a selected-index result on Unity's main thread; legacy callbacks also switch through Unity's Awaitable scheduler. The editor simulator is for exercising application paths; it is not a substitute for device permission, notification-delivery, review, or native-build validation.

Sample and support

Import Mobile Services Samples from Package Manager. Its four scenes—Overview, Haptics, Notifications, and Links—share one sample player; use its README for scene prerequisites and build tooling.

See docs, CHANGELOG.md, and issues.

About

Mobile platform services for Unity: native UI, notifications, and gesture detection

Topics

Resources

Stars

10 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages