正在加载视频...

视频加载失败

At Uber, one bug reaching production could cost millions in a single day. So quality was solved with headcount. Rooms of people would manually tap through the app before every release. Request a ride, add a card, cancel a trip, in 50+ languages, release after release. Now coding agents...

377,204 次观看 • 26 天前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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 Enga

23,963 次观看 • 2 个月前

the future is not the app store a 6 minute rant vibe coding tools have one problem no one's talking about anyone can make an app but no one can release an app posting on tiktok is instant, posting on youtube is instant what if posting a video on tiktok took 2-7 days and a panel of individuals who have NEVER posted a tiktok on their own, determined if your video was "tiktok-like" welcome to the 2025 app store, where this is the case let me explain a long time ago, when the first few iphones were released, apple had a tough battle motorola and blackberry were great competitors with phones people loved apple decided to open up the app store, and invite devs to come create whatever they wanted the app store was created by people like me, iBeer, Paper toss, Bump. these are my founding fathers. people who treated engineering as art. they didn't care about being cool they cared about making their friends look cool and using iBeer made you look cool the catch was -> iBeer was only available on the iPhone as hundreds of these iPhone exclusive apps were released thousands, hundreds of thousands, and millions flocked to use an iPhone small, focused, creative apps made the iPhone what it was but as soon as the iPhone became incumbent, the doors shut. tight. new rules. new regulations. new taxes. i spent the last 6 days working on an app we release an app a week at Danger Testing, bringing back that old energy. making the internet fun again i didnt sleep much, and even with the trauma the app store has put me in before ~ i had faith. that they would do right by this work I put in I was wrong They haggled with me for a few days on the type of data I was storing, which was none ~ (they would know that if they were engineers) Then at the last minute mailed it in with a rejection, with the words "this app is not app like" a sentence that means nothing Guideline 4.2 - Design - Minimum Functionality this is a guideline they hide behind anytime they have decided internally they don't feel an app should be released, but don't want to tell you why you leave me stranded. no where to go, no improvements to make, just go away there's a huge opportunity waiting to happen in apps right now for the first time apps can be cultural commentary, apps can be viral and ephemeral APPS CAN BE EVERYTHING YOUTUBE VIDEOS CAN BE software is fast, software costs nothing everything is lined up except the app store as it stands isn't a platform, it's a government and your average vibe coder is not going to push through a rejection, let alone 20+ rejections -> which i received on my first app of the year millions of apps will be made the success of these apps should be dependent on distribution, not on if some dude thinks its legit This revolution will NOT happen if the doors we have to go through are owned by the app store We need something new, something true and beautiful and welcoming Danger Testing wants everyone to be an appstar This tweet is not on the heels of a single rejection It's on the heels of hundreds of app store rejections in a lifetime A battle to provide the world with what I know it will love But a battle filled with friction at every turn due to the suits I remember being at a hackathon and making this app with andrea The judges ranked us last place, said the app was too goofy Today the last iteration of that app got 25+ million views across the internet This is the new world A group of dudes sitting behind a table don't get to decide our reality, we get to create it Fight back Don't ever allow yourself to be subjected by non shipper losers with no courage The cavalry isn't coming We are the cavalry Let's fight

los (appstar)

85,931 次观看 • 9 个月前