Repository files navigation How does Server Side Swift Workout in the Real World?
Brief overview of Heartwitch: The inspiration behind gBeat
Introduction to gBeat: A health and fitness live streaming app
Unified Language Ecosystem
Type Safety Across the Stack
Performance Benefits
Apple's Ecosystem Integration
Growing Server-Side Swift Community
Simplified Deployment and Scaling
Developer Productivity
Future-Proofing
Case Study: gBeat's Experience with Full Stack Swift
How the applications work
Integration with Apple Watch
User experience highlights
Implementation across iOS and watchOS
Challenge: Sign in with Apple not available on Apple Watch simulator
The challenge of discovering local development servers in full stack development
Specific issues with Apple Watch development
Introduction to Sublimation: A Swift package solution
Ngrok integration (initial approach)
Bonjour implementation (ultimate solution)
Impact on gBeat development
Developing a companion iPhone app for the AppStore
Implementing WatchConnectivity
Synchronizing workout data
Challenges and solutions
Impact on overall user experience
Choosing VueJS as the frontend framework
Implementing TypeScript for improved type safety
Utilizing Vite for build tooling
Webpack configuration for advanced scenarios
Challenges and solutions in creating a responsive fitness streaming interface
Android integration
Creating a White Label app - Issues with React Native and how Swift addressed them
Developing a Chrome Extension for YouTube Workouts
Deploying to Heroku
Setting up Continuous Integration with GitLab and GitHub
OpenAPI Integration
React Native XCFramework/Node Module
Protobuf
Hack Watch Networking
Hosting Options
Other Apple Platforms
Other Watch Platforms
Recap of key learnings
Encouragement for attendees to explore Full Stack Swift for their projects
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
You can’t perform that action at this time.