Webtoon and e-book app
We developed the app for a content service where webtoons, published comics, and novels are read in one place. The service takes serialized titles from several content suppliers and posts new episodes every day, and readers follow them on PC, the mobile web, and the app. Readers stay with images and documents for long stretches, so a stuttering scroll or a downloaded title in the wrong state breaks the reading itself. The work covered the webtoon viewer, the screens that open several document formats, and the on-device storage for content status, downloads, and reading history.
A webtoon viewer where scrolling and page turns do not stutter
The webtoon viewer is a screen for reading long vertical artwork by scrolling down. Scrolling, page transitions, and content loading decide most of the reading experience, so while building the layout and main interactions we focused on keeping those three flows steady. Because readers stay with a title for a long time, the loading and screen transitions they meet most often were checked again on their own.
Document viewing that opens published comics and novels in other formats within one app
To let readers open published comics and novels in the same app as webtoons, we integrated several document viewing components for PDF and e-book formats. Each format draws text and images on screen differently, so those differences were checked one by one. Readers turn pages the same way inside the app without needing to know which format they are reading.
An on-device database rebuilt around the state of downloaded titles
The webtoon app keeps the content status, download details, and reading history of downloaded titles in an on-device database. That record holds which episodes were downloaded and how far the reader got, so when it drifts, the reader downloads an episode again or loses their place. The existing structure was causing problems in screen layout and local data handling, so the database structure was redesigned to handle those three kinds of information reliably.
A storage rule that separates light values from data that must last
The webtoon app decides where data lives by what kind of data it is. Light values that do little harm if lost, such as favorites, go to the device's settings store, while data that must last and stay consistent goes to the server and the on-device database. With a clear rule for what goes where, whoever maintains the app later can find and change the data more easily.
Highlights
A webtoon viewer with refined scrolling, page turns, and loading
Document viewing that opens webtoons, published comics, and novels in one app
A storage structure that files content status, downloads, and reading history by their nature
Insights
GA4 client_storage: 'none'은 정말 쿠키를 막을까?
두 달 전 이 블로그에 「GA4 쿠키 없이 쓰기」라는 글을 썼습니다. clientstorage: 'none' 으로 쿠키 저장을 끄고, 자체 분석이 쓰던 익명 ID 를 clientid 로 넘기면 쿠키 0개로 GA4 를 쓸 수 있다는 내…
GA4 Measurement Protocol: gtag.js 없이 서버에서 이벤트 보내기
랜딩 페이지의 전송량을 파일 단위로 쪼개 보다가, 가장 큰 파일이 우리 코드가 아니라는 것을 알았습니다. Google Analytics 의 gtag.js 였고, 방문 한 번에 176KB 를 받고 있었습니다. 페이지 전체가 1,094K…
중소 제조업 AI 도입 순서: DX를 먼저 끝내야 할까?
공장을 가진 중소·중견 제조기업 16만여 곳 가운데 스마트공장을 도입한 곳은 19.5%입니다. 회사가 작을수록 이 비율은 더 떨어집니다. 중소벤처기업부가 2025년 4월에 낸 제1차 스마트제조혁신 실태조사 결과입니다. 그림: 기업 규…
Next.js loading.tsx와 404: 버튼이 화면보다 먼저 살아나게 하기
관리 화면 왼쪽 위에 사이드바를 접고 펴는 ☰ 버튼이 있습니다. 폭 하나 바꾸는 버튼인데, 대시보드에서 누르면 2초 넘게 아무 반응이 없었습니다. 레이아웃만 바꾸는 일이 왜 이렇게 오래 걸리는지부터 들여다봤습니다. Next.js 16…