As a young engineer with a deep curiosity for tech, I have always been fascinated with world of mobile development. Few years ago, I had the opportunity to explore Android Studio and build a simple Notes app. I enjoyed the process till I couldn't because my aging computer soon became a roadblock, forcing me to put my mobile development dreams on hold. After any small modification to my codebase, the Gradle Build would take long, frustrating hours to complete. I had to pivot into other areas of technology that would demand less from the PC.
Now, with a more powerful PC at my disposal, I am thrilled to rekindle my passion for mobile technology. This journey has led me to the HNG program.

Why HNG11?

So, to get started in this journey, I decided to enroll for the 11th edition of this fast-paced bootcamp for learning digital skills. It's focused on advanced learners and those with some pre-knowledge. I would get the opportunity to work with other coders, designers, product managers, and even video marketers to create innovative mobile solutions.

First Challenge

The inaugural task for us mobile development interns is to explore and discuss the various mobile platforms and their associated software architecture patterns. In this article, I will delve into three of the most popular options: Flutter, React Native, and Android Studio, highlighting the pros and cons of each.

Flutter

This is the platform I am really interested in mainly because of the fact that just a single codebase can be compiled into high-performance, visually attractive, and native applications for not just mobile alone, but for web, desktop, and even embedded systems. It is Google's open-source mobile app Software Dev Kit (SDK) that uses the Dart programming language and provides a rich set of pre-built widgets for building beautiful UIs. Here are some of the pros and cons of this platform:

Pros:

• Fast development times with hot reload feature

• Comprehensive documentation and growing community

• Ideal for MVP development and cross-platform apps

Cons:

• Dart is a relatively new language compared to JavaScript and Java

• Fewer plugins and libraries compared to React Native and Android Studio

• May lag behind if designs vary significantly between iOS and Android

React Native

A JavaScript framework developed by Facebook for building native mobile apps using React. It allows developers to build mobile apps using only JavaScript and React, with native components rendering to the device's native platform.

Pros:

• Vast ecosystem with a large community and many libraries and plugins

• Ideal for teams comfortable with JavaScript and React

Cons:

• Performance can be slower than native apps due to the JavaScript bridge

• Updating to newer versions can be challenging

• Documentation is not as comprehensive as Flutter's

Android Studio

This is Google's official environment for developing native Android apps. It provides a comprehensive set of tools for building, testing, and publishing. It supports both Kotlin and Java programming languages. Developers can choose the language that best suits their preferences and project requirements.

Pros:

• Allows for building native Android apps with Java or Kotlin

• Provides a flexible and easy-to-use Gradle-based build system

• Includes templates for Google services and various device configurations

Cons of Android Studio:

• Focused solely on Android development, not cross-platform

• Requires more time and effort to build and maintain separate iOS and Android codebases

In conclusion, the choice between Flutter, React Native, and Android Studio depends on the specific needs of your project and the skills of your development team. Flutter is an excellent choice for cross-platform development with a focus on performance and UI, React Native is ideal for teams comfortable with JavaScript and React, and Android Studio is the go-to choice for building native Android apps.

As I embark on this exciting journey with the HNG11 program, I am eager to explore these mobile development platforms further, learn from experienced professionals, and contribute to the creation of innovative mobile solutions that can positively impact people's lives.

Thank you for reading. Watch out for more juicy contents from this space.

Heck,I have made this mistake a couple of times and was frustrated every time. You already know why, but for those that don't, the size of a node_modules folder can be very heavy due to the dependencies (or npm packages) that are being used in a particular project.

Very funny but true.😆 Just don't underestimate the size of your node_modules folder.

Here is the simple way one can avoid pushing the folder:

• Create a .gitignore file inside your project folder. This file is a text file that tells Git which files or folders to ignore in a project.

• Inside this file, you must specify the file/folder you want to ignore. In this case, the node_modules folder. We can do this by writing in the file:

/node_modules

• Save the file.

This is how it should look like in your favorite text editor.

Now, you can go ahead!🚀 Push that code to your Git repository without having the dreadful folder tag along. Yes! We can avoid the reality of this meme.😁

I hope this read was fun as well as informative.😩 If so, I'mma catch y'all on the next one.

Danke Schön 🙏