Location-Based Cafe Information Platform (Boogakcong)

Project Overview

Boogakcong is a location-based web platform that helps users discover nearby cafes and compare cafe information and estimated walking times at a glance. It combines map-based cafe search with reviews and a community board, while providing dedicated workflows for regular users, cafe owners, community managers, and service administrators.

The platform was developed as a team project for Pusan National University’s Database course in the fall 2024 semester. Beyond displaying cafe listings, the project modeled members, cafes, reviews, posts, and cafe-owner registration and deletion requests as relational data, then connected them to complete user-facing workflows.

Mobile interface combining a Kakao map, nearby cafe list, and estimated walking time from the user's current location.

Core Features

Location-based cafe discovery: Displays cafes on a Kakao map and retrieves the address and details of the selected location.
Nearby cafe data import: Uses Kakao Local category search to collect nearby cafe data for the platform.
Cafe details: Provides contact and address information along with Wi-Fi availability, outlet count, table capacity, notices, and short reviews.
Reviews and community: Allows authenticated users to leave short reviews and create, view, edit, or delete image-based community posts.
My Page: Brings profile data, authored reviews, and authored posts together with direct editing and deletion controls.
Owner and administrator workflows: Lets cafe owners request registration, updates, or deletion, while managers approve requests, moderate members and content, and inspect service statistics.

Architecture and Data Flow

Next.js client → REST API → Spring Boot services → PostgreSQL

User and cafe coordinates → Kakao Maps / Local / Mobility APIs → Map, nearby cafes, and estimated travel time

Post image → Multipart request → AWS S3 → Stored image URL

The frontend uses Next.js and TypeScript for pages and API integration, with MUI providing a mobile-oriented interface. Authentication state and access tokens are coordinated through Jotai and browser storage. The backend exposes domain-specific REST APIs with Spring Boot and Spring Data JPA, secured through JWT authentication and role-based authorization. PostgreSQL stores members, cafes, reviews, posts, and owner requests, while AWS S3 manages uploaded post images.

My Contributions

Based on the public repository’s commit history, my work focused on the following frontend features and backend API integrations:

Connected the login and registration interfaces to the authentication APIs
Built My Page for profile information, authored reviews, and authored posts
Implemented interfaces for viewing, editing, and deleting short reviews
Implemented cafe registration/deletion requests and administrator approval screens
Built the community manager console for monitoring members, reviews, and posts
Built the operations console with visualized cafe and post statistics
Controlled the visibility of actions and management features by user role

Because user-facing and administrative screens shared the same API while exposing different operations, I focused on keeping UI state and request flows consistent across authentication and role changes.

Results and Takeaways

The completed workflow connects cafe discovery, reviews and community posts, owner requests, and administrative approval and moderation through a unified data model. The project demonstrated how a relational schema becomes real create, read, update, and delete operations across UI components and REST endpoints, and how authentication and authorization shape both the interface and API behavior in a multi-role service.

Working with separate frontend and backend repositories also required aligning API response contracts with domain types and integrating maps, directions, and object storage into one cohesive user experience.

Tech Stack