Álvaro García Pizarro

I used Claude throughout the development process as a coding assistant and thought partner. It helped me debug tricky SwiftUI issues, refactor complex logic, write cleaner code, and think through architecture decisions. When I got stuck on something like Live Activity state management or WatchConnectivity sync problems, Claude helped me understand the issue and find solutions faster. It also helped with copywriting, from onboarding text to App Store descriptions. Having an AI that understands context and writes quality code made the whole project move much faster.

I used Xcode for the entire development of Tweny. It handles everything from writing SwiftUI code to designing the Apple Watch app, building widgets, and testing Live Activities. The integrated simulator lets me test on different iPhone and Watch models without needing physical devices for every case. Instruments helped me optimize performance and catch memory issues early. For native Apple development, there is really no alternative.

I chose GitHub because it keeps everything organized and safe. All the code, version history, and project files live in one place. I can track every change I make, roll back if something breaks, and keep a clean record of how the app evolved over time. For a solo developer, having that safety net is essential. It just works and I never have to worry about losing progress.

I chose GitHub because it provides a reliable, transparent, and developer-friendly ecosystem for managing the project. Using Git allows me to track changes cleanly and collaborate efficiently, while GitHub Actions automates builds, tests, and deployments so updates are consistent and error-free. The Releases section makes it easy to share versioned builds and changelogs with users, ensuring everyone always has access to stable, well-documented updates.

I chose the Qwen model as the default starting in version 1.2 because it delivers an ideal balance of speed, accuracy, and lightweight performance. It runs efficiently on-device, uses very little storage, and responds quickly even on less powerful hardware. This makes it a perfect fit for an offline AI assistant where reliability, low resource usage, and a smooth user experience are essential.

chose Next.js because it offers a fast, reliable, and flexible framework for building modern web experiences. Its built-in routing, server-side rendering, and strong performance optimizations make it easy to deliver a smooth, SEO-friendly site while keeping the codebase clean and maintainable.