Software Engineer — iOS / Apple Platforms
I build on Apple platforms, and my work centers on clarifying where product requirements meet system design — then turning that into something a team can actually ship.
At GO Inc. I work on the iOS app for GO, a taxi-hailing app in Japan, focusing on architecture improvements in a large codebase and technical design for new initiatives. Swift and Objective-C are my core, and when needed I work across the boundary into the backend (Go) and product requirements.
As a side engagement or contract, I can help in situations like these:
Representative work, limited to what is publicly available. Linked talks and articles are in Japanese.
On a large, long-running commercial app, I work on feature development, technical design for new initiatives, and architecture improvements. I work through requirements and implementation plans with PMs, designers and backend engineers, and carry them through to implementation in the iOS app.
I presented the strategy for replacing the iOS app's dependency injection framework and rolling it out across the whole app without stopping the largest amount of parallel development the team had ever had.
Experience untangling dependencies and responsibility boundaries in a grown application, and migrating step by step without stopping development.
While adding English support to many existing screens alongside day-to-day feature work, the team ran into problems that also involved coordinating with PMs and designers. I presented those problems and the solutions, centered on how we managed UI strings.
Experience bringing a change that cuts across many screens and features into a live, large app, in coordination with other roles.
Using the taxi app's calling feature as the case study, I presented implementation techniques for delivering a smooth calling experience with CallKit.
Experience designing and implementing Apple platform APIs to fit product requirements in a large iOS app.
Slides · Talk abstract · Video
On the backend team I developed in Go and handled a project end to end, from defining the API requirements to the client-side implementation.
Experience thinking beyond the iOS app itself — API design and the split of responsibilities with the backend — and implementing it.
I took part in building the conference's official app as a staff member, and wrote about the design of its networking layer and its MVVM / RxSwift architecture.
Outside of work I also build my own products and tools, mostly on Apple platforms, and publish them on GitHub.
A tool for running AI coding agents such as Claude Code inside an isolated macOS VM (with Xcode and the iOS Simulator) or a Linux container. Inside a macOS guest booted with Virtualization.framework, the agent can go as far as xcodebuild test without touching the host. Only the working directory is shared, outbound traffic is limited by an allowlist enforced on the host, and the design decisions (ADRs) and security reviews are public. I gave a talk about it at iOSDC Japan 2026.
Designing and building the isolation, permission and network boundaries for a new area: AI coding agents meeting Apple's development environment.
An experimental app that, instead of computing trust as a score, records what actually happened — proposals, agreements, signatures — as a history signed by the people involved. It uses P-256 signatures (CryptoKit) and local storage with SwiftData, and the server (WevoSpace, Swift / Vapor) is designed as a coordination layer rather than the source of truth.
GitHub: h1d3mun3/wevo · GitHub: h1d3mun3/wevo-space · App Store · Introduction (DEV Community)
More repositories are on GitHub.
Talks and articles are in Japanese; titles below are translated.
Lightning talks on Swift language design:
I have been on the staff of iOSDC Japan, a large iOS developer conference in Japan, since around 2018, and I am now part of the core staff that runs it. In 2019 I helped build the official conference app, and I have also spoken at the conference and written for its official pamphlet.
Inquiries about side projects, technical advisory and one-off consultations are welcome. It helps if you include some background, what you would like to discuss, and the expected duration or frequency.