professional-work
Outdoor advertising agency platform — keeping map exploration and details together
I worked on a map-based web app for discovering wall spaces and viewing images and reviews. I connected map interactions and detail routes, and built admin search, project-management and login-return flows.
Keeping details in view while exploring a space
The outdoor advertising agency platform lets people discover wall spaces on a map, view images and reviews, and apply for projects. I worked on the user web app’s map, detail screens and frontend foundation, as well as the admin frontend.
After selecting a space, users needed to keep its details available while opening images or reviews. I configured Next.js parallel routes and default slots for this, and refined image-ID routes and review-data integration.
On the map, I connected Naver Maps to search results, markers and details, with separate behavior depending on location permission for nearby discovery. I also worked on the monorepo migration and route and build foundations supporting these screens.
Preserving a place to return to in the admin
I built project application, approval and management screens. With TanStack Router, I stored search criteria in the URL and connected them to server pagination.
When moving authentication to httpOnly cookies, I considered what happens when a session interrupts a task. If token refresh failed, I preserved the current GET screen’s path and search criteria as the return destination after login. This restored the screen context rather than automatically replaying the original request.
Map discovery and administration serve different tasks. Looking back, both raise a question about preserving selections and search context through navigation. My contribution was the frontend supporting those exploration, detail and management flows.