Code Once, Pin Everywhere: Multiplatform Widgets for Android & iOS - Andrea Della Porta

Value of the Information & Strength of the Argument

The talk provides high value by offering a concrete, tested solution to a common problem. The speaker backs his claims with real-world examples, open-source apps, and a live demo. He clearly explains the trade-offs and honestly presents the limitations imposed by the platforms. The argumentation is solid: he systematically breaks down the duplication points, shows the seam, and then dives into the ‘messy truths’ that developers will encounter, including specific numbers for refresh budgets and memory limits. His reasoning is structured and evidence-based, making a convincing case that sharing widget logic is not only possible but often advisable, provided the native UI is kept native.

Scientific Rigor, Source Quality, Title Accuracy

The scientific rigor is strong. The speaker references official documentation (e.g., Apple’s 40-70 refreshes, Android’s 15-30 min intervals) and mentions observed crash logs for the memory limit, which he clearly labels as observed rather than documented. He also cites examples of open-source apps that already use this pattern. However, he does not provide direct links to these references during the talk, and the only sources listed in the YouTube description are the conference websites. The title is perfectly matched with the content, as the talk is exactly about writing code once and using it for both platform widgets. The presentation is well-structured, with code examples and a live demo, supporting his points with practical evidence.

The title accurately reflects the content: the speaker demonstrates how to write once and use for both Android and iOS widgets, sharing all logic while keeping native UIs.

8/10

The talk is based on practical experience and real code, with specific numbers from platform documentation and observed crash logs. Some figures (e.g., 30 MB memory limit) are observed but not officially documented, which slightly lowers the absolute reliability.

Markers derived by PSI from the transcript: the creator did not define chapters.

• 00:15Introduction and setup of the problem: widgets are back, but building them twice is a headache.
• 03:00Duplication breakdown: fetch, domain, update policy, glue.
• 07:00Introduction of the 90/10 rule and the seam.
• 10:00Why Compose Multiplatform cannot be used for iOS widgets (archived view tree).
• 13:00The snapshot concept: a widget is not an app.
• 20:00Live demo of MatchPin showing shared code driving both widgets.
• 25:00The leash: refresh budgets and Android/iOS limitations.
• 34:00Memory limit corner: 30 MB ceiling in iOS extensions.
• 45:00Verdict: when to share and when to keep native.

• NDC Conferences — Conference official website
• NDC Oslo — Event page

• Apple WidgetKit Documentation — Confirms iOS widget architecture and refresh budgets.
• Android Glance Documentation — Confirms Android widget development with Compose-based Glance.
• Kotlin Multiplatform Official Guide — Supports the concept of sharing logic across platforms.
• Touchlab Sky GitHub — Provides the tool for bridging Kotlin flows to Swift, as mentioned in the talk.