Cross Platform Mobile Fishbowl
summary
Report from Trifork testing Xamarin across two projects: core networking and models deliver 75–80% shared code but custom native UI eats the savings; one project implements offline sync, another uses Unity for game-like UIs. A proof piece ships fast — 48 hours to build native color-picker for the London Eye with 80% code reuse — and clients love it, yet complex UI tweaks and platform quirks still require native work and extra debugging.
AI-written summary · about
chapters (25)
- 0:00Cross-platform mobile intro
- 1:29Samarind Forms vs Samarind
- 3:34When cross-platform helps
- 6:27Choosing the right tool
- 9:18Team skills matter
- 12:10Q&A with Samarind
- 13:56Deciding tech for project
- 14:39Samarind cost for new teams
- 16:03Samarind performance
- 17:48Samarind benefits beyond code
- 19:54Samarind vs native experience
- 20:57Teams and licensing
- 22:05Code quality and async
- 23:11Language preferences
- 25:42Personal journey with Samarind
- 26:25jQuery Mobile project
- 31:45When hybrid apps make sense
- 32:48Developer experience with jQuery
- 35:44First Samarind impressions
- 37:31Why teams use familiar tech
- 39:21Hybrid vs native UX
- 40:46Hybrid performance at scale
- 42:27Hybrid app context today
- 44:57Platform nuances in cross-platform
- 46:23Startup advice: one platform first
related talks
57mCross Platform Mobile with XAML and MVVM
42mCross-platform mobile apps development
54mSucceeding with Xamarin
54mTechniques in creating great cross platform apps.
41mWhat's Next for Cross Platform Mobile Development?
41mCross-Platform Fireside Chat
39mWorking Across Platforms
34mBuilding mobile applications with .NET Xamarin