![]() This worked well, but it was implemented outside of the mobile domain which made long-term maintenance challenging and required CLI knowledge to use. Initially, we integrated a mobile tophatting tool directly into Dev so that mobile developers can use commands like dev ios tophat to test changes. At Shopify, we use another internal tool called Dev, a powerful CLI interface for bootstrapping the codebases we work on. The Tophat tool took on different forms over the years. We built a desktop macOS application called “Tophat” that lives in the system menu bar. We created tooling that provides a seamless and interactive tophatting experience to contributors. What if we leveraged the mobile infrastructure we already have in place and make tophatting mobile changes as easy as a click of a button, without even pulling the branch? As you might imagine, needing to constantly stash changes, switch branches, and wait for Xcode or Android Studio to build a project adds up to countless hours of lost time. Instead, Shopify used emoji to convey the state of a PR review, posting a tophat emoji to indicate that the changes were not only reviewed, but also tophatted locally to validate that they work as expected. We call this process “tophatting,” a term that originated in a time when GitHub did not yet support PR reviews. What was the longest, most mundane aspect of your development workflow? Chances are, you probably remember waiting for the app to compile every time you wanted to test out a change.Īt Shopify, manually testing every GitHub pull request (PR) we ship as part of code review is part of our culture. Think back to the last mobile project you worked on. ![]() It’s no secret that we love creating purpose-built internal tools that make complex tasks virtually effortless. To build great mobile apps at scale, you need a great developer experience. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |