DEV Community: Suraj Abasaheb Baride

🚀 React Native 0.82: Ushering in a New Era

Suraj Abasaheb Baride — Fri, 10 Oct 2025 12:19:50 +0000

Published: October 8, 2025

🌟 What’s New in React Native 0.82?

React Native 0.82 marks a significant milestone as the first version to run entirely on the New Architecture. This release sets the stage for future updates by removing the option to disable the new architecture, signaling the end of the Legacy Architecture era. Key highlights include:

New Architecture Only: The entire framework now operates on the New Architecture, enhancing performance and maintainability.
Experimental Hermes V1: Introduces an opt-in feature for Hermes V1, aiming to improve JavaScript execution speed and efficiency.
React 19.1.1: Upgrades to the latest React version, bringing improvements and new features.
DOM Node APIs: Adds native support for DOM Node APIs, expanding the capabilities of React Native for web-like functionalities.

🧠 Why This Release Matters

The transition to the New Architecture is a strategic move to streamline the codebase, reduce bundle sizes, and pave the way for more efficient development processes. By removing legacy components, React Native aims to:

Enhance performance across platforms.
Simplify the development workflow.
Ensure long-term maintainability and scalability of the framework.

🔄 How to Use React Native 0.82

✅ Upgrading an Existing Project

To upgrade your project to React Native 0.82, follow these steps:

Use the React Native Upgrade Helper: This tool provides a detailed guide on code changes between versions.
Update Dependencies: Ensure all dependencies are compatible with React Native 0.82.
Test Thoroughly: Run your application to identify and resolve any issues arising from the upgrade.

✅ Creating a New Project

To initialize a new project with React Native 0.82:

npx @react-native-community/cli@latest init MyProject --version latest

For Expo users, React Native 0.82 will be available as part of the expo@canary releases. The next stable SDK, SDK 55, will ship with React Native 0.83.

📅 When Was It Implemented?

React Native 0.82 was officially released on October 8, 2025, marking the culmination of extensive development and testing. The decision to remove the Legacy Architecture was made to ensure a more streamlined and efficient framework moving forward.

🔧 Additional Features and Fixes

Optimized Debug Build Type for Android: Enhances the debugging experience on Android devices.
Web Performance APIs (Canary): Introduces experimental support for web performance APIs, allowing developers to monitor and optimize performance metrics.
Breaking Changes: Some APIs from the Legacy Architecture have been deprecated. Developers are encouraged to transition to the new architecture to avoid potential issues in future releases.

🛠️ Known Issues

React Native Reanimated Compatibility: Users of React Native Reanimated may encounter compatibility issues with React Native 0.82. A workaround involves manually patching certain files, but an official update is recommended for full compatibility.

🔗 Resources

🧭 Conclusion

React Native 0.82 represents a pivotal shift towards a more modern and efficient framework. By embracing the New Architecture and introducing experimental features like Hermes V1, React Native continues to evolve, offering developers enhanced tools and capabilities for building high-performance applications.

📢 New Google Play Rule: 16 KB Page Size Requirement

Suraj Abasaheb Baride — Fri, 26 Sep 2025 09:59:16 +0000

Starting November 1, 2025, all app submissions on Google Play must comply with the 16 KB page size requirement for native binaries.

This applies to:

New apps uploaded to the Play Store

Updates to existing apps
👉 Only if the app targets Android 15 or higher

🧩 What is “16 KB page size”?

Android apps rely on memory pages—chunks of memory that the OS loads to run native code.

On modern ARM CPUs, 16 KB pages are the new standard for better performance and memory efficiency.

If your app’s .so files (native libraries) don’t support this, you may face:

App rejections on Google Play ❌

Poor performance on Android 15+ devices ⚠️

⚛️ React Native Developers – Good News

React Native core is already 16 KB compliant ✅

BUT: if you use native modules or third-party SDKs (e.g., camera, analytics, AR, video players), you must check their binaries.

🔍 What You Should Do

Check Native Dependencies

Look inside:

android/app/src/main/jniLibs/

or in your Gradle build outputs for .so files.

Verify Page Size
Run:

readelf -h libexample.so | grep 'Page size'

Expected output:

Page size: 16384

(16384 bytes = 16 KB)

Confirm with Library Authors

If a library isn’t compliant → update it.

If no update is available → request the maintainer to recompile with 16 KB support.

✅ Meaning for React Native Projects

Safe:

Apps using only React Native + JS/TS code.

Action Needed:

Apps that integrate native SDKs (ads, payments, video, AR/VR, etc.).

👉 Double-check compliance before Nov 1, 2025, or your app submission will be rejected by Google Play.

📌 More details: React Native 0.81 Blog

🚀 My Tech Interview Journey at Q2Pay Technology – React Native Developer Role

Suraj Abasaheb Baride — Thu, 17 Jul 2025 12:28:44 +0000

Hey Dev Community 👋

I'm excited to share my recent experience of joining Q2Pay Technology Pvt. Ltd. as a React Native Developer. I officially started on 14th July, and so far, it has been an amazing learning journey with a great team and a supportive work culture. 💻✨

This blog is not just an update — I want to share my full interview process, from the first HR call to the final manager round, and especially the technical interview that tested my knowledge in React Native.

✅ My Interview Process at Q2Pay Technology
Here’s a breakdown of the steps I went through:

HR Call Round
A basic introduction, resume discussion, and role alignment.
Assignment Round (Online)
I was given a technical assignment to complete in React Native, which tested my practical coding skills, UI implementation, and app structure.
Technical Round (Online)
This round was conducted by Neha Ma’am from the tech team — and this was the most interesting and challenging part!
She asked me a variety of questions based on React Native and JavaScript concepts, including:
What are Hooks in React?
Explain Promises in JavaScript.
How do you handle errors in your code or API calls?
How do you build an APK for Android?
Tell me about your last project and its tech stack.
Difference between ScrollView and FlatList.
How do you manage state in React Native apps?
These questions really tested my real-world understanding of building mobile apps with React Native.
Final Managerial Round
This was more focused on soft skills, team collaboration, problem-solving attitude, and future goals.
Offer and Onboarding
And finally, I got the offer! 🎉 I joined the team officially on 14th July.
👨‍💻 My Current Role
At Q2Pay Technology, I'm working as a React Native Developer, building cross-platform apps for iOS and Android. With 2+ years of experience, I continue to learn every day, thanks to a knowledgeable team lead and friendly teammates.

What I really appreciate here is:

The learning culture
Supportive mentors
Real project challenges
Growth-oriented environment
🔑 Takeaways from My Interview Experience
If you’re preparing for a React Native Developer interview, here are some tips based on my experience:

Brush up on React hooks like useState, useEffect, useCallback, etc.
Understand how Promises and async/await work in JavaScript.
Know how to handle errors in API calls and debug mobile apps.
Be ready to explain your previous projects, architecture decisions, and problem-solving approaches.
Practice building and deploying apps — like generating APKs and iOS builds.
Know the difference between ScrollView, FlatList, and when to use them.
Be clear with state management, both local and global.
✍️ Final Words
I'm truly grateful for this opportunity at Q2Pay Technology and excited for what's ahead. I hope sharing my journey helps someone preparing for a React Native tech interview or just getting started in their development career.

If you found this useful or have any questions — feel free to connect!
Let’s keep learning and building, together. 💡📱

🚀 Why You Should Start Building Side Projects as a Developer

Suraj Abasaheb Baride — Thu, 26 Jun 2025 18:39:56 +0000

As developers, we often focus on our day jobs or academic assignments. But building side projects can completely transform your skills, mindset, and even your career.

Here’s why working on your own ideas, outside of client or company work, can be a game-changer.

🔧 1. Learn by Doing
Classroom theory and tutorials are great, but nothing beats the learning that comes from building your own app or website.

“Tell me and I forget. Teach me and I remember. Involve me and I learn.” – Benjamin Franklin
When you face real-world bugs and user interactions, you grow faster than you'd expect.

🌱 2. Grow Your Portfolio
Every side project you build is proof of your skills. Instead of just saying "I know React," you’ll be able to show a blog, a to-do app, or even a full-stack SaaS product.

✅ Hiring managers love self-driven developers.

👑 3. Boost Confidence & Creativity
Working on what you want means more creative freedom. You choose the tech stack, the design, the problem — and when you finally launch it?

That’s confidence unlocked. 💪

🖼️ Example Project Image:
My portfolio site built using React + Tailwind.
💼 4. Stand Out in Job Interviews
Most developers list college projects or tutorials on resumes. But if you can speak about your own real-world side project, you immediately stand out.

Talk about:

What problem it solves
Tech stack
Challenges & wins
Live demo link
💸 5. It Might Make You Money
Some side projects evolve into startups or passive income streams. From selling templates to launching an app — many devs turn projects into profit.

Example:

indiehackers.com is full of real stories where devs turned their ideas into dollars.
🧰 Tools to Try:
Frontend: React, Vue, Next.js
Backend: Node.js, Firebase, Supabase
Design: Figma, Canva, Tailwind CSS
Deployment: Vercel, Netlify, Render
🔚 Final Thoughts
Side projects help you:

Learn faster 🧠
Show off skills 💼
Build confidence 🚀
Have fun 🎮
Maybe even earn 💰
So, don’t wait. Pick an idea, open your editor, and start building. Your future self will thank you!

📸 Bonus Image for Motivation:
🙌 What Are You Building?

Comment below and share your side project ideas!
Let’s inspire each other.

My Journey Through the Interview Process and Assignment Challenge

Suraj Abasaheb Baride — Fri, 23 Aug 2024 11:20:00 +0000

Introduction

Recently, I embarked on a new opportunity by applying for a position at a company that intrigued me. After submitting my application, I was thrilled to receive a call from the company for an interview. The interview process was rigorous, and it challenged my technical knowledge across various domains. I would like to share my experience, the challenges I faced, and how I approached the assignment that followed the interview.

The Interview: A Technical Deep Dive

During the interview, I was asked a wide range of questions that tested my understanding of core concepts in web development. The questions covered several topics, each requiring a strong grasp of fundamentals and practical knowledge. Here’s a breakdown of some of the key areas discussed:

Arrays and Manipulation
I was presented with an array, [1, 2, 3, 4, 5], and asked how to manipulate it to display only specific elements, such as 1, 2, 5, 6. This required a solid understanding of JavaScript array methods and how to efficiently manipulate data structures.

Media Queries for Responsive Design
The interview also delved into CSS, particularly focusing on media queries. I was asked to explain how media queries can be used to create responsive designs that adapt to different screen sizes. This part of the interview highlighted my ability to ensure that web pages are accessible and visually appealing on all devices.

React Components
A significant portion of the interview was dedicated to React. I was asked to explain the concept of components, how they are used to build user interfaces, and the importance of reusability in component-based architecture. This discussion also touched on the state and props in React, demonstrating my ability to manage data within an application.

Context API in React
Another React-related topic was the Context API, a powerful feature for managing state across the application. The interviewer wanted to gauge my understanding of how Context can be used to avoid prop drilling and manage global state effectively.

Array Methods: Map and Filter
The interviewer asked about array methods like .map() and .filter(). I was required to explain how these methods are used to iterate over arrays and create new arrays based on certain conditions. This question tested my functional programming skills in JavaScript.

Bootstrap Grid System
Finally, the conversation touched on the Bootstrap grid system. I was asked how to utilize Bootstrap's grid to create responsive layouts that adjust across different screen sizes. This required a good understanding of the grid system, including containers, rows, and columns, as well as how to use responsive classes like col-sm, col-md, and so on.

Moving to the Next Round: The Assignment

After the interview, I eagerly awaited feedback from the company. I was pleased to learn that I had been selected to move on to the next round, which involved completing a technical assignment. This assignment was a practical test of my ability to implement the concepts discussed during the interview.

The Assignment: Fetching and Displaying Dog Images

I was provided with an API endpoint for the assignment: . The task was to build a web application that retrieves data from this API and displays it in a user-friendly manner. The assignment had two key requirements:

History Section: I needed to create a section that stores and displays the history of images retrieved from the API. Each time a new image was fetched, it had to be added to this history section.

Card Section: The main section of the application had to display the current image fetched from the API. This card section needed to be visually appealing and functional, allowing users to see the dog image clearly.

Completing the Assignment

I completed the assignment within one day, ensuring that it met all the specified requirements. I utilized React to build the application, leveraging its component-based architecture to create a clean and maintainable codebase. The application was designed to be responsive, ensuring that it looked great on all devices.

I also implemented additional features, such as:

Local Storage: The history of images was stored using local storage, ensuring that the history persisted even if the page was refreshed.
Error Handling: I added error handling to manage any issues that might arise during the API call, ensuring a smooth user experience.
After completing the assignment, I delivered it to the company for evaluation. Below are the links to the GitHub repository containing the code and the live deployment of the application:

Live Output: Dog Image Task - Deployed on Vercel

Conclusion

This experience was both challenging and rewarding. The interview process pushed me to demonstrate my technical knowledge and problem-solving skills, while the assignment allowed me to apply those skills in a practical scenario. I am proud of the work I delivered and look forward to hearing back from the company regarding the next steps in the hiring process.

I want solve my problem plz help me

Suraj Abasaheb Baride — Thu, 11 Apr 2024 06:29:16 +0000

Running 'gradlew :app:assembleRelease' in /home/expo/workingdir/build/android
Downloading https://services.gradle.org/distributions/gradle-7.6-bin.zip
10%
20%.
30%
40%
50%
60
%.
70%
80%.
90%
100%
Welcome to Gradle 7.6!
Here are the highlights of this release:

Added support for Java 19.
Introduced --rerun flag for individual task rerun.
Improved dependency block for test suites to be strongly typed.
Added a pluggable system for Java toolchains provisioning. For more details see https://docs.gradle.org/7.6/release-notes.html To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.6/userguide/gradle_daemon.html#sec:disabling_the_daemon. Daemon will be stopped at the end of the build > Configure project : Invalid Java installation found at '/usr/lib/jvm/openjdk-17' (Common Linux Locations). It will be re-checked in the next build. This might have performance impact if it keeps failing. Run the 'javaToolchains' task for more details. FAILURE: Build failed with an exception.
What went wrong: A problem occurred configuring root project 'InstaCaver1'. > Could not determine the dependencies of null. > Could not resolve all dependencies for configuration ':classpath'. > The new Java toolchain feature cannot be used at the project level in combination with source and/or target compatibility
Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights.
Get more help at https://help.gradle.org BUILD FAILED in 56s Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.