Googlers is a company that creates products intended to create opportunities for an extensive audience, regardless of their location across the globe. The company values diverse perspectives, imaginations and non-conformity to predefined norms and impossibilities. The goal is to build products while incorporating uniqueness of each individual involved in this process, aiming to make their products accessible and useful to all.
Do You Manage Peer Insights at Google?
Access Vendor Portal to update and manage your profile.
Espresso handles the main UI thread pretty well, so I don't get as many timing issues compared to other frameworks I have used. Being able to set breakpoints in my tests and step through while looking at the UI state saves me tons of time. The test recorder is useful for getting started quickly, but I always clean up the code it generates because it's messy. The logging integration is solid, as I can filter through logs efficiently when tracking down why a test failed on a specific device. Running parameterized tests with different data sets is straightforward, which helps when I need to validate the same workflow across multiple scenarios.
The best things about this product are: 1. The best IDE for Kotlin projects 2. It offers preconfigured emulators for testing and you can quickly build and publish Google Apps 3. It has LLM to help you build faster
I liked the easy to use IDE, code intelligence support, debugging & program run in simulator, and refactoring features of Android Studio. It is an all-round platform for developing android applications.
Build times are really slow. Even small changes require rebuilding everything, and that kills my productivity during active test development. The idling resource concept sounds good in theory, but I'd end up having to modify my actual app code just to make tests stable. Background operations and network calls constantly cause flaky tests because Espresso can't track everything that's happening. Emulators can be deceiving, animations run differently, touch events don't always work the same, and then I'd get bug reports from real devices that were never caught. There's no built-in way to do visual comparisons either, so I have to use third-party tools for screenshot testing.
The three things I don't like are: 1. It has a high system resource consumption 2. It has a big learning curve 3. And it is quite complex building systems like Gradle
It requires more computer resources for specially RAM and CPU; the size of the installation file is generally large and takes more time to download since it contains SDK and other required tools, Has limited language support (I am comfortable in C# but I cannot develop app using this tool with C# coding)