Vibhav Kumar’s Post

One of the reasons for unresponsive UI is the continuous allocation and deallocation of memory, which leads to frequent GC runs. By using the bitmap pool concept, we can avoid it. The best part is that Image-Loading libraries like Glide, and Fresco use this bitmap pool concept. So, always use Image-Loading libraries. Delegate all the image-related tasks to these libraries. Learn about Bitmap Pool in Android: https://lnkd.in/dHFTZJYQ

how to create aab file in android More Here: https://lnkd.in/dRyyzVNX

One of the reasons for unresponsive UI is the continuous allocation and deallocation of memory, which leads to frequent GC runs. By using the bitmap pool concept, we can avoid it. The best part is that Image-Loading libraries like Glide, and Fresco use this bitmap pool concept. So, always use Image-Loading libraries. Delegate all the image-related tasks to these libraries. Learn about Bitmap Pool in Android: https://lnkd.in/dHFTZJYQ #androiddev

💡 Pro Tip: Avoid Passing Arguments in Fragment Constructors! If you're working with fragments in Android, you've probably heard that it's best not to pass arguments directly in fragment constructors. 🚫 But why? Here's the issue: when fragments are recreated (due to configuration changes, system-initiated destruction, etc.), Android uses the default no-argument constructor. Any arguments passed in a custom constructor are lost, leading to unpredictable behavior or crashes. 💥 ✅ Solution: Use setArguments() with a Bundle to pass data to fragments. This approach is lifecycle-safe, as Android retains the arguments across configuration changes. 🚀 This small change can save you hours of debugging! Have you encountered this issue before? Let's share best practices to avoid those tricky lifecycle bugs! #AndroidDev #MobileDevelopment #FragmentTips #AndroidTips #LifecycleManagement

How can I find all unused files in an Android project? Click on the “Code” menu and select “Inspect Code”. In the “Inspect Code” dialog, select the scope you want to inspect (e.g. “Whole project”). Check the “Unused declaration” option and click “OK”. The code analysis will run and generate a report of all unused files, classes, and resources in your project. https://apksync.com/

view-source: 🔧 To find out if a digitised image is #IIIF-compliant or not, look for the words IIIF, or manifest, or /full/ in the source code of its web page. Just add "view-source:" in front of the URL to see the source code (this also works on Android). #clevertool

I recently tackled the HTB “Saw” Challenge, a journey through Android application reverse engineering to uncover a hidden flag. 1. Bypassing initial launch checks 2. Granting necessary permissions 3. Reverse engineering native code 4. Solving an XOR puzzle 5. Accessing protected files The key takeaways involve: 1. Understanding app behavior through code analysis 2. Utilizing ADB for interacting with Android devices 3. Applying reverse engineering skills for hidden logic 4. Importance of permission management in app analysis This challenge was a great learning experience in applying reverse engineering techniques to Android apps. It emphasized a systematic approach and understanding both high-level and low-level code. If you're interested in Android reverse engineering, check out the full write-up here: https://lnkd.in/gUm5-UtU #HTB #ReverseEngineering #AndroidSecurity #MobileSecurity

Day 12 of my Android journey: Today, I learned about Toasts in Android and various methods of the Toast class. The most commonly used one is the static makeText(Context, CharSequence, int) method, which returns a Toast instance. We can change the position of the toast message using the setGravity method. I also learned how to create a custom toast layout and set it to the toast instance using the setView method, which takes in a View reference. Additionally, I learned how to create AlertDialogs in Android; these are essentially default Dialog boxes.

𝐀𝐍𝐑 𝐢𝐧 𝐀𝐧𝐝𝐫𝐨𝐢𝐝 & 𝐢𝐭𝐬 𝐭𝐲𝐩𝐞𝐬 Discover what ANR is in Android and the various types of ANR issues that can occur in the Android Sub-System. Check out the insightful article here: https://lnkd.in/gBJSvs6w

In Flutter, the ConstrainedBox is a widget used to impose additional constraints on its child widget. It allows you to control the size and layout behavior of the child by specifying minimum and maximum width and height. These constraints ensure that the child widget adheres to the specified size limits, but the child is still free to define its size within those limits.