FlyWise

FlyWise was the travel-planning concept I worked on to bring itineraries, voice input, image-assisted place discovery, language options, and translation-oriented ideas into one interface.

Abstract flight path with waypoints, directional aircraft symbol, and itinerary cards

Problem

I wanted to reduce the constant switching between search, translation, recognition, and itinerary tools while planning a trip.

Constraints

I needed several input modes to feel like parts of one user journey
I treated account and preference data as private
I could not assume that third-party recognition or translation behavior worked without testing it
I kept unverified assistance features framed as intended flows rather than completed capabilities

Technical decisions

My surviving project notes list React and Vite for the client; I no longer have the source to re-check that implementation
My surviving notes also list Node.js and Express for the service layer
They also list Firebase for data and identity, which I have not re-verified
I designed account access as the entry point for the personalized planning concept

Evidence

I verified that the public demo still reaches a complete login screen without entering credentials
I kept the original interface screens that show the intended trip-planning flow
I no longer have the source needed to verify itinerary generation, recognition, translation, or personalization end to end

What I learned

FlyWise taught me to prove one complete planning path before presenting a wide set of intelligent features as a finished experience.