Landseer Enga
@LandseerEnga • 2,388 subscribers
your app should never break @tryrevyl
Shorts
Videos
Excited to share what the team’s been working on the past month. Introducing: Atlas 🌍 For far too long, mobile apps have lacked a design source of truth. We've heard this from company after company: no one knows what the app really looks like. And now that coding agents have made changes 10x faster, keeping up manually is impossible. So we made a map of all the screens in your app, automatically updated.
Landseer Enga18,993 просмотров • 3 дней назад
everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.
Landseer Enga23,599 просмотров • 6 дней назад
Agents can one shot mobile apps, but testing is still the bottleneck. So we built a CLI that gives Claude Code the one thing it was missing - eyes and hands The best part? t's fully vision-based: - No scripts, no selectors, no element IDs - It interacts with the app exactly like a human would Claude now writes code → tests it on the app → sees what broke → fixes it Spawn a cloud agent, go to sleep, and wake up knowing it actually worked.
Landseer Enga86,808 просмотров • 3 месяцев назад
React Native devs: Your background agent can now hot reload in the cloud. We built a CLI that tunnels your local Expo app to a cloud simulator so every code change shows up live. Claude Code can now: - Edit a component - Watch it render live - Confirm the change No simulator on your laptop. No screenshots. A live dev loop, in the cloud, at scale.
Landseer Enga29,247 просмотров • 2 месяцев назад
Built a lightweight mobile SDK that lets our QA agent know exactly what's happening under the hood. It tracks: - CPU/memory performance - Network requests & failures - Screen transitions - Tap gestures - Full distributed traces Give an agent this level of context and it stops guessing why a new feature isn't working. It just reads the trace and fixes the code.
Landseer Enga30,621 просмотров • 3 месяцев назад
Больше нет контента для загрузки