Svelte Native in production
summary
Built a native iOS/Android client with Svelte Native layered on NativeScript and reuses server-side logic from SvelteKit endpoints. Pure business logic and a thin fetch-based data layer run unchanged on mobile, yielding roughly 60% code reuse; DOM-backed UI components do not, so native views are reimplemented. App is functionally successful in development, internal testing invites planned, with public release targeted for May–June. The project keeps a single-language stack to avoid context-switching across web and mobile.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06The Project Context
- 2:08Why Svelte Native?
- 3:19Svelte Native vs React Native
- 4:29Code Reusability Challenges
- 6:19Extracting Business Logic
- 7:52Defining Business Logic
- 9:38Refactoring for Reusability
- 10:31Data Fetching Layers
- 11:27Component Abstraction
- 12:29Leaky Abstractions
- 12:58Realities of UI Reuse
- 14:17Development Balance
- 14:40Conclusion
related talks
25mGoing Native
21mCreate an Engaging Native Mobile App with Vue and NativeScript
20mDissolving Boundaries: The Fusion of React app and Native Apps!
44mCooking with NativeScript-Vue
45mReuse your web skills to build native apps with NativeScript
09mGoing Native: Reusing Code
25mOne Source to Rule them All
22mNativeScript and CodeSharing