My Role
Creator
Product Design
User Experience
Interaction
Developement
My Tools
Figma
Notion
Xcode
Cursor
The Idea: Simple Task System Across Devices
Projectero started as a personal challenge to design and build a simple but effective task management app that worked seamlessly between iOS and macOS.
The goal was to strip out unnecessary complexity found in most project management tools and focus on what matters: creating, organizing, and tracking tasks efficiently. Each task lives within a project and can include notes, due dates, and status updates.
The key differentiator was native reminders — a feature missing in many task apps that rely solely on notifications or external integrations. I wanted reminders to feel like a first-class part of the workflow, not an afterthought.
From Concept to App Store
I designed and built the app myself using Cursor AI as a coding assistant and SwiftUI for the interface. The first version shipped to the App Store successfully, followed by two approved updates that refined stability and improved the task creation flow.
Shipping a fully functional, user-facing product end-to-end, from concept and design to code and release, was a milestone in validating both the design system and my development process.
The Challenges That Followed
Not everything worked perfectly. iCloud syncing proved to be a major technical hurdle. While local data performed reliably, syncing across devices failed intermittently and created data inconsistencies.
The macOS build also introduced unexpected friction. The app ran successfully in Xcode’s testing environment but repeatedly failed App Store validation. After multiple review cycles and code adjustments, I decided to ship the iOS version only until the cross-platform architecture could be stabilized.
Rather than forcing a fragile sync experience, I prioritized maintaining a reliable single-device app and started exploring alternative solutions. Supabase emerged as a more scalable option for syncing and storage, offering clearer control over schema and fewer limitations than Apple’s native iCloud environment.
What Went Right
Research
App usage data
Even before launch, informal testing with users highlighted key needs:A clean UI that focuses on tasks, not featuresIntuitive interactions like quick-add and long-press to organize projectsA frustration with other apps requiring login or showing adsThis feedback validated the decision to keep the interface minimal and account-free.
Development Observations
Working hands-on with SwiftUI and iCloud surfaced countless micro-interactions and technical decisions that directly shaped the design. Each implementation challenge became a user insight, guiding how to better structure flows, error states, and syncing logic.
User stories
As a user, I want to add and edit tasks quickly, without navigating through menus.
As a user, I want my tasks to sync across devices without setting up an account. As a user, I want a lightweight app that doesn’t distract me from the work itselfIterations
Each feature in Projectero was built incrementally, tested through real usage, and reworked when it didn’t feel right.
I simplified task input, adjusted hierarchy to prioritize action over structure, and refined the task editor over multiple versions. Syncing logic went through several refactors, informed by trial-and-error testing across devices and operating systems.Early feedback
Initial testers appreciated how quickly they could get started without logging in or configuring anything.
• Users liked the responsive UI and said it felt “native and fast.” • The lack of distractions was seen as a benefit, not a limitation. • Several noted they’d “use this just because it doesn’t ask me to create an account.”Follow-Up Feedback & Data
After launching on the App Store, feedback remained consistent:
• Users appreciated the speed and simplicity of the interface. • Feature requests focused more on syncing reliability than added functionality. • The iCloud issues, while frustrating, helped prioritize improvements for the next phase.What I Learned
This project taught me more about system design and engineering constraints than almost anything else I’ve worked on.
Building a full production app revealed how design decisions break or hold up under real-world conditions — sync conflicts, App Store rejections, and data edge cases included.
It reinforced that “done” in software design doesn’t mean perfect, it means stable, testable, and ready to evolve.
My Role
Creator
Product Design
User Experience
Interaction
Developement
My Team
Me
My Tools
Figma
Notion
Xcode
Cursor
The Idea: Simple Task System Across Devices
Projectero started as a personal challenge to design and build a simple but effective task management app that worked seamlessly between iOS and macOS.
The goal was to strip out unnecessary complexity found in most project management tools and focus on what matters: creating, organizing, and tracking tasks efficiently. Each task lives within a project and can include notes, due dates, and status updates.
The key differentiator was native reminders — a feature missing in many task apps that rely solely on notifications or external integrations. I wanted reminders to feel like a first-class part of the workflow, not an afterthought.
From Concept to App Store
I designed and built the app myself using Cursor AI as a coding assistant and SwiftUI for the interface. The first version shipped to the App Store successfully, followed by two approved updates that refined stability and improved the task creation flow.
Shipping a fully functional, user-facing product end-to-end, from concept and design to code and release, was a milestone in validating both the design system and my development process.
The Challenges That Followed
Not everything worked perfectly. iCloud syncing proved to be a major technical hurdle. While local data performed reliably, syncing across devices failed intermittently and created data inconsistencies.
The macOS build also introduced unexpected friction. The app ran successfully in Xcode’s testing environment but repeatedly failed App Store validation. After multiple review cycles and code adjustments, I decided to ship the iOS version only until the cross-platform architecture could be stabilized.
Rather than forcing a fragile sync experience, I prioritized maintaining a reliable single-device app and started exploring alternative solutions. Supabase emerged as a more scalable option for syncing and storage, offering clearer control over schema and fewer limitations than Apple’s native iCloud environment.
What Went Right
Research
App usage data
Even before launch, informal testing with users highlighted key needs:A clean UI that focuses on tasks, not featuresIntuitive interactions like quick-add and long-press to organize projectsA frustration with other apps requiring login or showing adsThis feedback validated the decision to keep the interface minimal and account-free.
Development Observations
Working hands-on with SwiftUI and iCloud surfaced countless micro-interactions and technical decisions that directly shaped the design. Each implementation challenge became a user insight, guiding how to better structure flows, error states, and syncing logic.
User stories
As a user, I want to add and edit tasks quickly, without navigating through menus.
As a user, I want my tasks to sync across devices without setting up an account. As a user, I want a lightweight app that doesn’t distract me from the work itselfIterations
Each feature in Projectero was built incrementally, tested through real usage, and reworked when it didn’t feel right.
I simplified task input, adjusted hierarchy to prioritize action over structure, and refined the task editor over multiple versions. Syncing logic went through several refactors, informed by trial-and-error testing across devices and operating systems.Early feedback
Initial testers appreciated how quickly they could get started without logging in or configuring anything.
• Users liked the responsive UI and said it felt “native and fast.” • The lack of distractions was seen as a benefit, not a limitation. • Several noted they’d “use this just because it doesn’t ask me to create an account.”Follow-Up Feedback & Data
After launching on the App Store, feedback remained consistent:
• Users appreciated the speed and simplicity of the interface. • Feature requests focused more on syncing reliability than added functionality. • The iCloud issues, while frustrating, helped prioritize improvements for the next phase.What I Learned
This project taught me more about system design and engineering constraints than almost anything else I’ve worked on.
Building a full production app revealed how design decisions break or hold up under real-world conditions — sync conflicts, App Store rejections, and data edge cases included.
It reinforced that “done” in software design doesn’t mean perfect, it means stable, testable, and ready to evolve.
Get in touch, or send me a cat video