Hi — Ray here, founder working in an adjacent space. This is a genuine question, not a pitch.
I was reading through mobile-devtools. The part that stood out is the way you frame the tools as both runnable projects and blueprints: Security Scanner, PR Review Bot, Visual Regression, Figma Design Checker, Greenlight, App Explorer — all using Revyl CLI to boot cloud devices and Claude Code to automate mobile workflows.
That seems like a specific open-source shape: useful to fork internally, but not necessarily the kind of repo where people naturally show up via issues and start contributing.
For these Revyl tool repos, have you found that getting the first useful outside contributors or serious users requires manual outreach into mobile engineering circles, or do the blueprint repos tend to attract the right people on their own?
A short reply is plenty.
Hi — Ray here, founder working in an adjacent space. This is a genuine question, not a pitch.
I was reading through
mobile-devtools. The part that stood out is the way you frame the tools as both runnable projects and blueprints: Security Scanner, PR Review Bot, Visual Regression, Figma Design Checker, Greenlight, App Explorer — all using Revyl CLI to boot cloud devices and Claude Code to automate mobile workflows.That seems like a specific open-source shape: useful to fork internally, but not necessarily the kind of repo where people naturally show up via issues and start contributing.
For these Revyl tool repos, have you found that getting the first useful outside contributors or serious users requires manual outreach into mobile engineering circles, or do the blueprint repos tend to attract the right people on their own?
A short reply is plenty.