I am building a single-codebase Flutter application that pairs with our motorized TV lift, an IoT module embedded in premium furniture. The device already exposes documented HTTP/RPC endpoints; the app simply has to speak those endpoints and present a working, no-frills interface. Scope – Platforms: the same build must run on both iOS and Android. – Core features: reliable device onboarding, responsive remote control (up, down, stop, presets), and straight-forward device management functions such as rename, delete, and firmware update triggers. – UI: keep it basic; polish and re-skin will be handled internally later, so clean separation between logic and presentation matters more than visuals. Deliverables • Flutter 3.x project with null-safety and well-commented code. • Typed client library wrapping the lift’s HTTP/RPC calls. • Onboard IoT devices via Wi-Fi SoftAP provisioning • Discover devices on the local network via mDNS / Bonjour • Store and manage multiple devices locally • Control each device independently (extend / retract) • Onboarding flow that discovers or inputs device IP, pairs, and stores credentials securely. • Control panel screen sending real-time commands and reflecting current lift status. • Device list & management pages persisting to local storage. • Build-ready iOS (IPA) and Android (APK/AAB) artifacts plus setup documentation. Acceptance The app must connect to a test lift on our LAN, complete the onboarding sequence, provision the device for home wifi, connect and rename the device, store the device locally, execute up/down/stop commands, and survive a full day of continuous status polling without memory leaks (verified via Flutter DevTools). Hardware context We’ll provide multiple physical test devices for development and QA: • Device: Shelly 2PM Gen4 • Use case: Contact-closure control of TV lifts • Local control via HTTP/RPC • Discovery via mDNS • Provisioning via SoftAP (device AP) Technical requirements • Flutter (required) • Strong iOS experience, especially: • Wi-Fi provisioning • NEHotspotConfiguration • Local network permissions and mDNS Android networking experience: • Wi-Fi APIs • Multicast / mDNS • Comfortable working with real hardware • Ability to design clean separation between logic and UI Nice to have • Prior IoT onboarding experience • Zeroconf / Bonjour familiarity • Experience debugging networking edge cases Technical references (for context) You don’t need prior Shelly experience, but these define the scope: Shelly RPC API (Gen2 / Gen4) https://shelly-api-docs.shelly.cloud/gen2/ Shelly Wi-Fi provisioning (SoftAP) https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/WiFi/ Shelly networking & discovery (mDNS) https://shelly-api-docs.shelly.cloud/gen2/General/Networking/ If anything is unclear about the HTTP/RPC spec, let me know early so I can share endpoint details and sample payloads.