Aleksander Mikucki
Aleksander Mikucki is an individual React Native engineer, developer-relations professional and open-source creator, not a company. His Screenmap project helps Expo/React Native teams preview the screens affected by a pull request by running the app in CI, capturing reachable screens and posting a visual review to the pull request.
At a Glance
- Expo and React Native development teams
- Mobile engineering and pull-request reviewers
- Designers collaborating with mobile teams
- Teams using GitHub Actions and simulator-based CI
- +1 more
AI Tools by Aleksander Mikucki
(1)Screenmap
Visual Diff Tool for React Native
Discussions
No discussions yet
Be the first to start a discussion about Aleksander Mikucki
Latest News
React Navigation made a first-class route provider, with provider detection and custom-provider support
Screenmap added analytics to the map viewer and excluded the project's own screenshotter traffic
Deep-link arrival checks, drifted-flow recovery and agent repair paths were added
The project was renamed from expo-map to Screenmap and the .scrmap bundle format and viewer branding shipped
Products & Services
The aleqsio/screenmap@v1 Action runs in a repository's GitHub Actions, maps or restores a baseline of the app, determines which routes a pull-request diff can reach, captures affected screens on a simulator and posts a sticky pull-request comment with screenshots, changed regions and a viewer link. Source: https://github.com/aleqsio/screenmap
A /screenmap Claude Code plugin that helps learn or map an Expo/React Native app locally, records flows and produces the shared .scrmap bundle. Source: https://github.com/aleqsio/screenmap
The browser viewer at app.screenmap.dev opens .scrmap bundles, shows the app's route/screen graph, replays flows and lets teams share a map with reviewers or designers. Source: https://github.com/aleqsio/screenmap
Market Position
Screenmap positions itself as an open-source, CI-native visual review and navigation-mapping tool for Expo/React Native. Its differentiators are route-aware suspect selection instead of recapturing an entire app for every PR, repository-owned screenshots, deterministic committed-flow replay, and a shared local/CI/browser map. The adjacent alternatives are manual simulator review, screenshot-regression tools and generic web preview systems; Screenmap is aimed specifically at mobile app navigation and pull-request context. Source: https://screenmap.dev/
Leadership
Founders
Aleksander Mikucki
React Native engineer and DevRel at Software Mansion; his personal site says he works on Expo SDK areas including Filesystem, Expo UI and Modules Core, and lists open-source projects including react-native-url-router and npx new-arch. His GitHub account is aleqsio and he is the copyright holder named in Screenmap's MIT license. Sources: https://aleqsio.com/, https://github.com/aleqsio/screenmap/blob/main/LICENSE
Founding Story
Screenmap was created to address the gap in mobile pull-request review: web pull requests commonly provide a preview URL, while mobile reviewers often have to install a build and find the relevant screen themselves. The initial vision was a CI-native, open-source map of an Expo/React Native app that shows every screen and highlights what a pull request changed, without requiring someone to write a test. Source: https://screenmap.dev/
Business Model
Revenue Model
Open-source, self-hosted tooling rather than a disclosed paid SaaS model. The MIT-licensed Action runs in the customer's own GitHub Actions, and the landing page says users pay for their own CI minutes and agent; the hosted simulator option is described as coming soon. Sources: https://screenmap.dev/, https://github.com/aleqsio/screenmap/blob/main/LICENSE
Target Markets
- Expo and React Native development teams
- Mobile engineering and pull-request reviewers
- Designers collaborating with mobile teams
- Teams using GitHub Actions and simulator-based CI
- Developers using Expo Router or React Navigation
- Visual review of Expo or React Native pull requests
- Mapping an unfamiliar mobile app locally
- Replaying and sharing app navigation flows with designers and reviewers
- Detecting which screens are affected by route or source-code changes
- Creating a reusable baseline of an app's screens in CI