Hey Ankit! This is a great part 2 in the series! I would recommend using a String constant for your baseUrl in RetrofitClient. This allows you to do something like this:
private final String baseUrl = BuildConfig.DEBUG ? “http://mydebugurl.com” : “http://myreleaseurl.com”;
I noticed in your example gif, the items in that list have their own backgrounds generated. Do you think that it’s possible to fade out the alpha channel? Or how does Plex overlap elements on the page effectively in that case?
Awesome breakdown of the individual components you had working on the app. Sensors are always a little weird to me but your explanation was clear and concise!
Can sensors run in the background while your phone is locked? Having the ability to lock your phone while the app tracks your steps would be great. Be sure to share if…
I found this really difficult while designing the layout, in addition to the point you made.
I found that if you use the tools namespace, it can help with making sure your layout looks the way you intend.
Hey! Thanks for the great explanation. Maybe I missed something, but in your example, if you call showProgressBar() at the end of your initProgressBar() method, it’ll be visible until you start typing.
I think that’s super neat! Flutter definitely is striking me as a solid cross platform tool. Having used Xamarin for about half a year now, I was drawn in by the rapid build times and editor support (go IntelliJ!).
Have you found any difficulties linking up any 3rd party Android libraries? I’m just curious, haven’t really…
I have had similar experiences with Xamarin. It’s a great tool in theory but it’s terrible for long term stability. I’m working on a fair sized project in it and my build times are 3–4 min on average, sometimes 10. And then VS will fail to correctly deploy the app, which causes me to get runtime errors like “Class R could not be found”.
Naming is something that is a constant skill to refine, but you did a really great job advocating why it’s important. I think one of the coolest examples of code readability I’ve seen is in this relative date-time helper: https://stackoverflow.com/a/1248/8157136. It’s probably a bit outdated now, but just goes to show that you’re right on the money when it comes to importance of code readability.
You hit the nail on the head about taking the time to teach not only tell. I’ve got a sinking suspicion that most of the software industry is not really following this mentality, yet there are some groups that are leading the charge on it and I think it creates a stronger comraderie between developers when we stop thinking of teaching someone as a waste of time.