app deployment to apple app store / live

Deduci App

A native iOS learning app that helps students turn voice memos into better questions for professors, reducing the gap between 'I know I am confused' and actually knowing what to ask.

EngineNative iOS frontend with full-stack backend services
TimelineOngoing

Pathway to App Store Connect

  • Rebuilt the original Java idea into a more flexible JavaScript and native-iOS-oriented product direction instead of leaving it as a one-off class artifact.
  • Built the SwiftUI experience around quick capture and low-friction academic follow-up.
  • Connected frontend and backend work through the trivi.dev personal project and used PostgreSQL plus Railway deployment workflows to support the full-stack infrastructure.
  • Integrated OpenAI API workflows to generate questions and later expanded the product into code-study and typing-game directions.
  • Used Unity as a mobile game-development direction for turning longer, costly de-dupe and question-production loads into playable screen takeovers instead of dead waiting time.
  • Treat Snapchat Lens Studio as a real prototyping skill for building camera-native interactions and testing lighter-weight engagement loops around product ideas.
  • Presented Trivi at the Shawnee Game Conference as part of the project’s academic and technical development.

Tools and context

  • Tech: SwiftUI, Native iOS, Node.js, TypeScript, PostgreSQL, Railway, Full-stack integration, Product design
  • Constraint: The product had to feel useful quickly. If the workflow felt abstract, over-engineered, or like another thing to study instead of a way to study, it failed.
  • Outcome: Turned a class-project idea into a sharper product story with real deployment, real data handling, and a clearer reason to exist.

Breakdown

Decision-making and implementation

Problem

Students often capture confusion but not the right follow-up

A voice note preserves the moment, but it does not magically become a good question. I wanted a tool that helped with that conversion instead of just storing more stuff.

Decision

Keep the workflow concrete and a little competitive

I tend to care more about tools when they feel active and engaging, not like digital worksheets. That shaped both Trivi and Deduci: make the transformation obvious and keep the experience lively.

Result

The product became more than a class build

What started as a functional class app became a deployed, evolving product with real technical decisions around APIs, PostgreSQL, Railway, and native iOS direction.