Build shape
Vehicle device companion app
Vehicle device companion app
TalkCar
A vehicle companion product where the app receives web commands, talks to the device socket, and returns the result.
AutomotiveHardwareWebView
Product brief
The product only works when the bridge between web, app, and vehicle device stays reliable.
TalkCar is a connected product that links the web, the mobile app, and a vehicle device. The app acts as a bridge: it receives commands from the webview, talks to the device, and returns results back to the web layer.
The repo shows login, a message library, downloads, firmware updates, enterprise approval, a webview bridge, and the socket protocol used to reach the device at 192.168.2.1:5050. It is a hardware companion product built around control clarity.
Scope
Problem
Problem
Because the phone can lose internet while attached to the device over Wi-Fi, the webview and socket flow had to stay stable.
Implementation
I combined a Flutter webview bridge, auth, downloads, library management, firmware updates, and the device protocol into one product flow.
Best fit
This fits control products and field connection apps where hardware, web, and mobile need to move together.
Technical structure
Product evidence
Primary stack
Flutter · hooks_riverpod · WebView
Data & sync
HTTP API · SharedPreferences · device state bridge
Operational surface
Firmware downloads · S3 buckets · device header injection
Stack
App shell
Flutterhooks_riverpodget_itpackage_info_plusdevice_info_plusintl
Bridge and networking
webview_flutterhttpconnectivity_plusshared_preferencesurl_launcher
Operational integrations
api.talkcar.nettalkcar.co.kr WebView pagesS3 firmware bucketS3 message bucket
Integrations
talkcar.co.krapi.talkcar.netAWS S3WebView bridgeConnectivity monitoring
Screens
Product evidence
Web
App
Need a similar product, internal tool, or launch-ready first version?
Send the current problem, scope, or a reference link. The next step can start from product structure and release scope.