Business or user problem

Create a reliable mobile control surface for connected grill hardware where real-time status, notifications, and device behavior needed careful coordination.

Technical constraints and architecture

  • Hardware communication required resilient state handling.
  • SDK and device behavior needed testing across mobile platforms.
  • User feedback and error states had to be clear during active cooking sessions.
  • Built a Flutter architecture for device state, telemetry, notifications, and control flows.
  • Integrated VIAM SDK and wireless communication paths with user-facing status handling.
  • Structured implementation around demos, review feedback, and release-readiness checks.

Role and ownership

  • Architected and developed the Flutter application.
  • Integrated VIAM SDK for real-time robot control and monitoring.
  • Implemented Bluetooth and Wi-Fi communication protocols.
  • Supported planning, estimation, stakeholder updates, feedback follow-ups, and release coordination.

Delivery and client communication

Client context

  • Connected-hardware product requiring close coordination between mobile app behavior, SDK integration, device feedback, and release readiness.

Discovery and requirements

  • Clarified product goals, users, and the mobile workflows that mattered most for smart grill control.
  • Converted approved requirements into implementation scope, feature notes, and release checkpoints.

Project plan and milestones

  • Broke mobile delivery into milestones covering core flows, integrations, QA, store readiness, and post-release checks.
  • Kept scope visible so new feedback could be triaged without losing release focus.

Sprint planning approach

  • Supported sprint planning, feature sequencing, story estimation, and acceptance-criteria preparation.
  • Kept implementation tasks connected to API readiness, design states, and QA coverage.

Estimation and ETA communication

  • Prepared practical delivery estimates based on integration complexity, platform differences, and testing risk.
  • Communicated ETA changes when blockers, dependency shifts, or feedback affected the plan.

Stakeholder cadence

  • Shared progress, blockers, dependencies, and implementation decisions with stakeholders during delivery.
  • Used demos and review points to gather feedback before release-critical decisions became expensive.

Risks, blockers, and dependencies

  • Tracked API readiness, third-party SDK behavior, device differences, offline behavior, and app-store requirements.
  • Escalated blockers with context, impact, and proposed next actions.

Client feedback and follow-ups

  • Captured client feedback, meeting notes, action items, and next decisions after reviews.
  • Closed the loop on changes through implementation notes, QA handoff, and release follow-up.

Release responsibilities

  • Prepared release builds, store-facing checks, and post-release monitoring support where applicable.
  • Coordinated fixes and follow-up actions after QA, stakeholder review, or public release feedback.

Approved outcomes

  • Delivered the mobile foundation for remote chef mode, live telemetry, error notifications, and user feedback loops.
  • Improved stakeholder visibility through milestone planning, demos, and tracked follow-up actions.