#webview

Learn how to safely handle Android WebView onShowFileChooser callbacks, overlapping requests, cancellations, and activity state limits.

Your website is already working well, compatible with mobile device? Why recreating the wheel, and...

Two Android payment bugs looked harmless: a white WebView and a foreground return. Neither meant what...

Building a Minimal Android WebView Wrapper App in Kotlin I recently needed a lightweight...

A WebView does more than display HTML. It can connect web content to application identity, cookies,...

com.myvitals.app, installed from the Play Store, icon and splash screen and everything, has almost no...

How to Build a Secure Android WebView Wrapper with Kotlin A practical guide to building a...

To be clear about the title up front: by 'native framework' I don't mean apps written directly...

라이브 방송을 보며 실시간으로 채팅을 주고받는 모듈을 만들고 다듬으며 겪은 문제들을 정리했다. 가상 키보드 대응, iOS 웹뷰 전용 버그, 자동 스크롤 알고리즘의 경쟁 상태까지 — 어떤 요구사항 때문에 어떤 선택을 했는지와 그 문제를 어떻게 원인 분석해서 풀었는지를 기록했다.

A postmortem of building and maintaining the live-chat module for a live-shopping app — virtual keyboard handling, iOS in-app WebView bugs, and the race conditions behind an auto-scroll algorithm that went through several rewrites.

A roundup of bugs and constraints I've actually hit on iOS Safari and in-app WebViews, grouped into five categories — input (Korean composition, focus, virtual keyboard), user gestures, scrolling, layout, and page-exit detection.

iOS Safari와 인앱 웹뷰 환경에서 실제로 마주쳤던 버그와 제약들을 입력(한글 조합·포커스·가상 키보드), 사용자 제스처, 스크롤, 레이아웃, 페이지 이탈 다섯 갈래로 정리했다.