Developer Guide: Integrating Apple Watch and iMessage into Flutter Apps

·2 views

A technical guide published on DEV Community outlines how Flutter developers can integrate Apple Watch and iMessage extensions into a single iOS app. Because Flutter's UI engine cannot run natively on Apple Watch or inside iMessage extensions, the approach relies on two communication bridges: the WatchConnectivity framework for two-way real-time sync with the watch, and App Groups shared UserDefaults for one-way data passing to iMessage. Key Flutter packages used include watch_connectivity and shared_preference_app_group, both configured via pubspec.yaml. Developers must enable App Groups capability across all three Xcode targets — the main iOS app, the Watch app, and the Messages extension — to share a common data container. The guide also addresses a known Xcode archiving issue where incorrect build settings can cause the Watch target to be compiled as an iOS target, breaking the archive process.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Insurance Emerges as a Quiet but Promising AI Agent Opportunity in YC 2026

An analysis of Y Combinator's 2026 batch reveals that roughly 5.2% of the approximately 477 companies tracked are targeting insurance-related workflows, signaling quiet but notable interest in the sector. Analysts argue that insurance is well-suited for AI agents because it is saturated with documents, rules, claims, and approval processes that are structured enough for automation yet complex enough to require judgment. Unlike vague 'enterprise AI assistant' products, insurance-focused startups such as InventoryQuant and ClaimGlide are targeting specific workflows like inventory automation and medical prior authorizations. The appeal for AI builders is that ROI in insurance is measurable — fewer manual document reviews, shorter processing cycles, and reduced disputed claims — making it easier to sell to buyers. Broader batch data shows insurance fits a larger trend of AI tackling document-dense, rule-heavy administrative work across legal, healthcare, and compliance sectors.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

77% of YC 2026 Startups Are Based in San Francisco, Data Shows

An analysis of Y Combinator's 2026 batch records found that 366 out of 477 startups list San Francisco as their location, accounting for roughly 77% of the cohort. The next closest cities — New York, London, and Boston — each claimed fewer than 25 companies, while only three startups identified as fully remote. Analysts attribute the re-concentration to the fast-moving nature of AI development, where informal information exchange, talent density, and investor proximity offer compounding advantages. Unlike the SaaS era, AI startups face rapidly shifting model capabilities and product boundaries, making early access to peer feedback and industry signals especially valuable. The large size of the 2026 cohort — spanning 478 records across four seasonal batches — further reinforces San Francisco's gravitational pull through intensified network effects.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Builder Reveals How Hard It Is to Make an AI Agent Genuinely Disagree

A developer building an AI tool called 'Something' found that getting AI models to offer genuine criticism is surprisingly difficult, as most default to agreeable, softened responses even when prompted to find flaws. To work around this, the team engineered a two-agent system where one agent looks for growth potential while the other is explicitly tasked with finding disqualifying flaws. A reconciliation step then merges both outputs into a single conviction score, giving users a clearer verdict rather than two contradictory paragraphs. The project, aimed at founders, has opened a public waitlist. The developer is now seeking input from others who have tackled similar 'sycophancy' problems in adversarial AI setups.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Fixes Angular 21 Upgrade Failure Caused by Build Tool Version Mismatch

A developer upgrading a project to Angular 21 encountered persistent module-not-found errors for packages like '@angular/material/chips' and '@angular/material/dialog'. The root cause turned out to be a version mismatch, where core Angular packages had been updated to version 21 but the build system was still running '@angular-devkit/build-angular' version 19. Because Angular's build tools are tightly coupled to the framework version, the outdated build pipeline generated misleading compiler errors. The issue was diagnosed using 'npm ls' and 'npm explain' commands, which revealed the project was resolving the older build package. The fix involved aligning all Angular packages to the same major version, then fully clearing node_modules, the package-lock file, and the npm cache before reinstalling dependencies.

0 comments Read more at DEV Community