Smartphones are quickly moving towards smaller bezels and larger aspect ratios. On these devices, display cutouts are a popular way to achieve an edge-to-edge experience while providing space for important sensors on the front of the device. There are currently 16 cutout devices from 11 OEMs already released, including several Android P beta devices, with more on the way.
The application needed to support functionality, which allowed the user to load more data on scrolling – known as LoadMore. When a user would request the application to load more data, the application could potentially encounter a network issue (such as network not available, extended latency, or timeout, etc). When this happened, the application would need to show a Retry button. If the user decided to tap the Retry button, the application would again fire a LoadMore event. This would in turn issue the API call to load more data.
Gradle provides two built-in mechanisms for tracing your build: --profile and --scan. The former produces a simple HTML report of task execution times. You can get a rough idea of where time was spent but are unlikely to glean any real insights. The latter sends a detailed report to Gradle’s servers (or to a Gradle Enterprise installation) with much more granular information. Task details are rendered on a concurrent timeline corresponding to their execution. For CI builds, I tend to want something more granular than --profile but I don’t like the idea of sending details of every build to Gradle with --scan. It seems entirely needless considering their plugin has all of that information locally but chooses to render it remotely.
When you build an app that has to deal with network calls, you almost end up writing the same boilerplate code in order to perform that. What if we try to automate and reduce the amount of code we need to write for a network call ?
Hello everyone! 👋 In this story I want to talk about the most common mistakes when adopting Clean Architecture. This story is the follow up after my latest medium Intro to App Architecture. Make sure to check it out if you are interested in what makes a good Architecture & why + how to achieve a more maintainable codebase.