Bixby Voice Capsule Development
Design a Bixby capsule with explicit actions, concepts, spoken training examples and local or simulator acceptance tests. Verify supported Developer Studio access before promising deployment.
Start with a task that has one clear, low-risk result. For example, let a user find an opening time for an already chosen location. Define the utterances, required concepts, expected response and what to do when information is missing or there are several matches. Verify the supported Bixby device, locale and Developer Studio flow using Samsung's current documentation. Documentation access alone does not establish that the signed-in account can preview or submit a capsule. ## Key Points - [Samsung Bixby capsule quick start](https://bixbydevelopers.com/dev/docs/get-started/quick-start) - [Samsung Bixby Developer Studio](https://corp.bixbydevelopers.com/dev/docs/dev-guide/developers/ide) - [Samsung Bixby developer guide](https://corp.bixbydevelopers.com/dev/docs/dev-guide/developers)
skilldb get mobile-app-skills/bixby-voice-capsule-developmentFull skill: 29 linesBixby Voice Capsule Development
Start with a task that has one clear, low-risk result. For example, let a user find an opening time for an already chosen location. Define the utterances, required concepts, expected response and what to do when information is missing or there are several matches. Verify the supported Bixby device, locale and Developer Studio flow using Samsung's current documentation. Documentation access alone does not establish that the signed-in account can preview or submit a capsule.
Build the concept and action contract
Model the location and date as inputs and the returned opening interval as an output. Keep the intent's goal distinct from the JavaScript implementation that performs the computation or calls an authorized service. Validate the arguments even when the planner supplied them. If the user omits a location, offer an explicit disambiguation or ask for the required input. Avoid storing spoken input unless the approved workflow needs it. Use synthetic data for the first capsule and keep credentials out of the source and debugger output.
Write spoken dialogue that is useful without the screen, and use views for optional additional detail. Include the actual timezone or local date only where the user needs it. Cover a supported set of natural paraphrases per locale, including changed word order, missing values and ambiguous names. Keep some utterances out of training so they serve as a real evaluation. A single trained demo phrase does not establish robust recognition or correct task planning.
Verify the plan and side effects
Use the authorized Studio simulator when available to inspect the execution graph, arguments, chosen action, returned concept and spoken output. Verify that a duplicate utterance and a delayed or unavailable backend produce bounded, understandable behavior. Where a capsule could make an external change, preserve user approval and verify the destination and final state separately. The read-only example should not create orders, appointments or other external records.
Record Studio and target environment, locales, exercised utterances, known unsupported cases and the exact artifact tested. If sign-in or simulator access is unavailable, run the pure action logic locally with mocked requests and record only what those tests show. Leave device invocation, marketplace approval and publication unverified until exercised through a supported, authorized path.
References and rights
Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.
Install this skill directly: skilldb add mobile-app-skills
Related Skills
Game Economy Design
Use this skill when designing virtual economies, progression systems, reward loops, or monetization structures for mobile games. Covers currency design, sink/faucet balancing, gacha mechanics, player spend segmentation, and live economy tuning. Trigger keywords: virtual currency, game economy, progression, gacha, loot box, IAP, monetization, reward loop, currency sink, whale, pay-to-win, economy balancing, pity timer.
Live Ops
Use this skill when planning live operations for mobile games after launch, designing content calendars, building battle passes or season passes, creating limited-time events and offers, segmenting players for targeted content, or managing update cadence. Trigger keywords: live ops, live operations, battle pass, season pass, limited-time event, content calendar, player segmentation, live service, hotfix, patch notes, live game.
Mobile Analytics
Use this skill when designing analytics systems for mobile apps, selecting analytics tools, defining event taxonomies, analyzing retention and funnels, or setting up crash monitoring and attribution. Trigger keywords: analytics, events, tracking, retention, cohort, funnel, DAU, MAU, attribution, SKAN, Crashlytics, A/B testing, feature flags, mobile metrics.
Mobile Development
Use this skill when advising on mobile app architecture, native vs cross-platform decisions, offline-first design, push notifications, deep linking, performance optimization, mobile security, or CI/CD pipelines for iOS and Android. Trigger keywords: mobile app, iOS, Android, React Native, Flutter, Swift, Kotlin, mobile architecture, offline-first, push notifications, deep linking, mobile CI/CD, Fastlane, mobile performance.
Measure Mobile Energy, Network and Background Location Cost
Compare energy, wakeups, location accuracy and network cost for mobile background work. Use on Android or iOS when changing location refresh, batching, caching or synchronization behavior.
Mobile Monetization
Use this skill when designing monetization strategies for mobile apps or games, including in-app purchases, subscriptions, ad monetization, paywall design, pricing psychology, and revenue optimization. Trigger keywords: monetization, in-app purchase, IAP, subscription, paywall, ad revenue, freemium, eCPM, ARPDAU, LTV, mobile ads, rewarded video, ad mediation, App Store commission, pricing strategy.