HYEONSEIM.

I have worked for years on the screens customers see inside the app, checking how each feature connects the app and WebView, from product entry to membership, points, login, and payment.

Entry across products

I built a WebView hub leading from an external service into other products in the app, with guidance tailored to each destination.

Points and membership

I organized the membership purchase list and descriptions. When redesigning the points screen, I also handled existing history routes and Korean and English display.

Login and payment

I contributed to changes in login and identity verification screens, then worked on the WebView flow for point top-ups, including the payment widget and return screen.

• WebView
• React
• TypeScript
• App bridge

In tools operators use every day, I considered how a change in one menu affects other tasks.

Session and menu state

I fixed UI issues around the order in which user details and menus update after login, expired sessions, and returning to an earlier screen.

Partner settlement lookup

I built screens for finding and viewing partner settlement summaries and trip records by statement.

Organizing operations tools

I migrated existing JavaScript and MUI features to TypeScript and Ant Design, and contributed to domain-specific Admin separation and monorepo integration.

• Operations Admin
• React
• TypeScript
• State management

At SWAP, I worked across customer touchpoints, from the initial web, WebView, and Admin builds to product discovery, first orders, payment details, and the business portal.

Orders and payment display

I separated accessory purchases from subscription inputs in first orders, connected receipt screens to server lookup results, and adjusted price display paths.

Login contract transition

With the team, I migrated bicycle customer login to a new OAuth2 contract and addressed token-state races just after login along with signup and consent flows.

Product discovery and business portal

I connected English product details and a quick-order path. For screens where businesses manage subscriptions, payment status, and payment methods, I handled access checks and post-payment return paths.

Bridge calls

I added Flutter callHandler and JavaScriptChannel.postMessage paths alongside the existing Android and iOS calls. Depending on the channel, I passed objects or serialized JSON, and tried the next method if a call threw synchronously. A successful call was kept distinct from completed native processing.

• React
• TypeScript
• SWR
• Zustand
• Flutter WebView

To connect voice AI with customer touchpoints, I reviewed vendors, product flows, and CX scenarios together.

Reviewing the introduction scope

I compared PoC scope, cost, and integration requirements for overdue-payment reminders and follow-up calls, and coordinated guidance scenarios with the CX team.

Entry point in the product

I connected the path into contract guidance from the returnable subscription completion screen and the return flow from the phone app.

Operational tracking

I tracked usage and costs after integration. I do not interpret call count as completed consultations or resolved issues.

• Product integration
• CX collaboration
• WebView

Call volume does not indicate successful consultations or resolved issues.

I documented how to use AI-assisted development according to each project structure and verification criteria, then shared the approach with the FE team.

Repository-specific rules

I created and improved development skills reflecting each project code structure and workflow.

Verification practices

I explained dependency boundary checks in the SWAP monorepo, checks appropriate to the changed scope, and configuration backup and recovery.

Reviewing generated code

I shared how I review AI-generated code for structure and complexity and choose only the changes that are needed.

• Development practices
• Code review
• Team sharing

Team productivity gains were not measured.

A public QA tool for checking local or staging web services inside iOS and Android WebViews.

Real WebView environments

I built a shell that opens screens in iOS WKWebView and Android WebView to check safe areas and navigation behavior.

Inspection panel

I brought viewport, storage, and log checks together in a web console.

• React Native
• WebView
• QA tool

I contributed to the handover and maintenance of an acquired shared-mobility service.

Maintaining an acquired service

I learned the operations context of the existing service and contributed to frontend maintenance.

• Acquired service
• Maintenance

On the Japan TF, I developed the website, back office, and WebViews and worked on screens and app connections for the Japanese service.

Japanese-language screens

I localized UI text in WebViews for the Japanese service.

App bridge

I contributed to the WebKit bridge that calls native functions from WebViews.

• International service
• WebView
• App bridge

I contributed to redevelopment of the website and back office for an acquired airport van service.

Customer and operations screens

After the acquisition, I contributed to frontend redevelopment of the customer website and operations back office.

• Acquired service
• Customer web
• Back office

I fixed a synchronization bug caused by changing options in a public library.

Dynamic option changes

I fixed the selected position in react-wheel-picker when options change dynamically with a one-line change. The contribution PR was merged on June 30, 2025.

• Open source
• React
• Bug fix