AssetStoreまとめ 割引情報 beta

- アセットの価格推移をリアルタイムにチェック -

Earn notification permission at the right moment. Schedule, localize, and measure relevant local notifications that bring players back to your Unity game or app on Android and iOS.LizardHouse Notifications is render-pipeline independent and is compatible with the Built-in Render Pipeline, URP, and HDRP. The included Soft Prompt prefab and demo interface use Unity UI (uGUI) and do not rely on custom shaders, render-pipeline-specific materials, or pipeline-specific rendering features.🔔 Turn notification permission into a player-return strategy.LizardHouse Notifications: Permission and Re-Engagement helps Unity developers ask for notification access at the right moment, bring players back with relevant local reminders, and understand the complete journey from first prompt to notification open.Instead of building permission logic, reminder scheduling, player-return cleanup, notification routing, localization, and analytics separately, you get one connected workflow for Android and iOS.You define the strategy and content. LizardHouse handles the lifecycle.🎯 Ask when players understand the valueThe native permission prompt gives you a limited opportunity. Make that opportunity count by asking after the player has experienced enough of your game to understand why reminders could be useful.Choose between the native permission prompt and your own branded Soft Prompt prefabShow the first prompt at app start, at a moment chosen by your game, or after meaningful engagementUse cumulative Active App Time, developer-defined Custom Events, or bothConnect any meaningful action, such as completing a level, puzzle, round, tutorial, or rewardContinue after Not Now with multiple Soft PromptsGive every follow-up its own design, message, delay, and engagement conditionsYou can build a thoughtful permission journey without locking your game into a fixed prompt design or asking every player at the same arbitrary moment.⏰ Create a complete re-engagement sequenceSchedule one reminder after a few hours or build a full journey that continues across days, weeks, or months.Every reminder can have its own:DelayTitle and messageNotification imageLocalizationQuiet Hours behaviorOne Time Only ruleNotification KeyCustom PayloadReminders are scheduled automatically around player inactivity, giving your game more opportunities to bring players back without requiring a campaign server.No notification backend. No dashboard account. No MAU fees. No internet connection required for the local re-engagement flow.🌙 Stay relevant and respect the playerA reminder loses its value when it arrives after the player has already returned.LizardHouse automatically removes reminders from the previous inactivity cycle when the player comes back, then creates a fresh schedule the next time they leave.It also cancels only the notifications it owns, allowing it to work alongside other notification systems in the same project.Use three per-notification Quiet Hours policies to decide whether a reminder should:Move to the end of Quiet HoursBe allowed during Quiet HoursPause its delay while Quiet Hours are activeThis gives each message the timing policy it deserves instead of treating every reminder the same.📲 Turn notification opens into useful actionsKnow which reminder brought the player back and decide what should happen next.The notification open callback provides the optional Notification Key and Custom Payload attached to that reminder. Use them to:Open relevant contentContinue a challengeHighlight an eventPresent a rewardNavigate to a specific screenConnect the return to your own game systemsNotification opens are handled during both warm and cold starts, with duplicate-open protection built in.You can also keep an in-game notification toggle synchronized with the player’s effective permission state and provide direct access to the operating system’s notification settings when needed.📊 Measure the complete journeySee where players accept, decline, return, or drop out through a consistent eight-event analytics funnel covering:Soft Prompt presentation and responseNative permission request and resultReminder scheduling and cancellationReminder due timeNotification opensChoose Firebase Analytics, connect your own analytics system through a generated integration script, or use the asset without analytics.The data stays in the analytics platform you choose. LizardHouse does not require an external account or send your notification analytics to its own servers.🌍 Fit every reminder to your gameReach players with content that belongs naturally inside your product.Use no localization provider, Unity Localization, or your own localization systemGenerate a ready-to-connect script for custom localizationAdd a different image to each reminderConfigure a custom Android status-bar iconSet the player-visible Android notification channel name and descriptionUse your own Soft Prompt prefabs, copy, animation, and visual styleLizardHouse provides the system without forcing its own branding, language, analytics platform, or prompt design into your game.🛠️ Built to save development timeConfigure the permission journey, notification sequence, Quiet Hours, localization, analytics, notification keys, and payloads from one dedicated Unity Window.The asset initializes automatically, keeps its state across scenes and app restarts, and validates the setup before saving. A focused public API keeps custom integration small.🎮 Test the experience before shippingThe included demo scene lets you:Preview your real Soft Prompt directly in the Unity EditorSimulate Custom EventsInspect the current permission strategyTest native permission and notification settings in a device buildVerify notification opens, keys, payloads, and state changes📚 Documentation, setup guides, integrations, and supportLizardHouse Notifications DocumentationYour game worked hard to earn the install. Give it a smarter way to earn the next session.A complete device-local notification permission and re-engagement workflow for Unity, with the editor tools, integrations, testing support, and source code needed to adapt it to your project.🎯 Permission JourneyPrompt options: Native Prompt or fully custom Soft Prompt prefabPresentation timing: App Start, After Conditions, or ManualEngagement conditions: Cumulative Active App Time, developer-defined Custom Events, or both using AND logicContextual follow-ups: Multiple Soft Prompts after Not Now, each with its own prefab, delay, and engagement conditionsPlayer-initiated activation: An in-game button or toggle can request native permission directlyPersistent progress: Permission journey state is retained across scenes, sessions, and app restartsOptional restart: The Soft Prompt journey can restart after previously enabled notifications are turned off🔔 Local Re-Engagement NotificationsInactivity-based scheduling: Reminders are scheduled when the player leaves or backgrounds the appFlexible sequences: Create one reminder or build a reorderable sequence across hours, days, weeks, or monthsIndividual configuration: Set a separate delay, title, message, image, localization, Quiet Hours policy, Notification Key, and Custom Payload for every reminderOne Time Only: Limit selected reminders to one completed delivery lifecycle per playerExisting-player reset: Allow a selected One Time Only reminder to be used again in a future game versionPlayer-return cleanup: Cancel reminders from the previous inactivity cycle when the player comes backSelective ownership: Only notifications scheduled by LizardHouse are cancelled or removedStable reminder identity: Internal notification identifiers remain connected to their reminders when the sequence is reordered🌙 Quiet HoursDevice-local timing: Quiet Hours follow the player’s local device timePer-reminder control: Every reminder can use a different Quiet Hours policyThree delivery policies: Respect Quiet Hours, Allow During Quiet Hours, or Pause Delay During Quiet Hours📲 Notification Opens and Player StateOpen callback: Detect when a notification scheduled by LizardHouse is openedRouting data: Receive an optional Notification Key and Custom PayloadApp lifecycle support: Handles notification opens during warm and cold startsReliable delivery: A pending open is retained until a subscriber is available, with at-most-once callback deliveryEffective state model: Enabled, DisabledByPlayer, PermissionRequired, PermissionDenied, Pending, and UnsupportedState updates: Respond when the effective notification state changesIn-game controls: Enable or disable reminders from your own Settings UIOS recovery: Open the app’s operating system notification settings when required🌍 Content and LocalizationLocalization options: None, Unity Localization, or Custom IntegrationCustom provider support: Generate a ready-to-connect localization integration script from the Settings WindowFallback content: Keep a title and message available when localized content cannot be resolvedNotification images: Assign a different optional image to every reminderNative image preparation: Images are processed and cached for native notification useAndroid small icon: Configure and validate a custom status-bar iconAndroid notification channel: Configure the player-visible Channel Name and Description while retaining a stable internal Channel ID📊 AnalyticsProvider options: None, Firebase Analytics, or Custom IntegrationCustom analytics support: Generate a ready-to-connect analytics integration script from the Settings WindowEight lifecycle events: Soft Prompt shown, Soft Prompt action, native permission requested, native permission result, reminder scheduled, reminder cancelled, reminder due, and notification openedStructured event data: Receive event names and read-only parameter collections through the custom analytics handlerData control: Analytics are sent only to the provider selected by the developerPayload privacy: Custom Payload content is not included in built-in analytics parametersNo LizardHouse telemetry: The asset does not require or send data to a LizardHouse analytics service🛠️ Unity Editor WorkflowDedicated Settings Window: Configure platforms, permissions, prompts, reminders, Quiet Hours, localization, analytics, images, keys, and payloads in one placeReorderable journeys: Organize Soft Prompt follow-ups and reminder sequences visuallyConfiguration summaries: Review important timing and behavior without expanding every itemSetup validation: Check dependencies, required content, integrations, prefabs, icons, conditions, and notification configuration before savingSafe configuration: Invalid setups are prevented from replacing the last valid saved configurationGenerated integrations: Create custom localization and analytics registration scripts directly from the WindowAutomatic preparation: Save Settings prepares notification images, Android icon resources, integration data, and runtime settingsAutomatic initialization: No notification manager needs to be added manually to a startup sceneOptional dependency isolation: Unity Localization and Firebase Analytics are not required by the core runtime🎮 TestingEditor Soft Prompt preview: Open and interact with the configured Soft Prompt prefab directly in UnityCustom Event simulation: Test engagement-event integration from the included demoConfiguration status: Inspect the selected permission strategy and current notification stateDevice test controls: Test native permission, in-game notification controls, OS Settings, state changes, notification opens, keys, and payloadsIsolated test reset: Restart the LizardHouse notification lifecycle without clearing the game’s own save data📦 Package ContentsFull C# source codeRuntime notification systemSettings and Setup Validation WindowDemo scene for Editor and device testingSoft Prompt example prefabsCustom localization integration generatorCustom analytics integration generatorOffline documentationComplete online documentation⚙️ Platforms and RequirementsSupported platforms: Android and iOSRequired package: Unity Mobile Notifications 2.3.0 or newerRequired UI package: Unity UI (uGUI)Optional integration: Unity LocalizationOptional integration: Firebase AnalyticsArchitecture: The core permission and local scheduling workflow runs on the player’s device without a LizardHouse backend, account, or MAU feeNative testing: Operating system permission and notification behavior is tested through an Android or iOS build📚 Documentation, Setup, Integrations, and SupportOpen the LizardHouse Notifications documentationOpenAI tools were used to review code for syntax and performance issues, assist with test planning, structure the documentation, and draft initial visual prototypes. LizardHouse defined all product requirements, architecture, workflows, and user experience. All materials were manually reviewed, revised, integrated into Unity, and functionally tested by LizardHouse. The asset contains no generative AI functionality and does not require an AI service at runtime.