DEV Community: Amit jha

(1/3) Nodejs With FirebaseAuth: The Right Way

Amit jha — Thu, 14 Jan 2021 12:31:07 +0000

PART 1/3

Hey there fellas! I'm back with another article and today we are talking about FirebaseAuth with Flutter and Express. I have encountered that a lot of articles online talk about using FirebaseAuth with flutter but not many of them talk about using your own server to manage the requests from your app while using FirebaseAuth. Today we will change that.

Before we being I would like to mention that I'm assuming that you know Flutter and JavaScript.

In today's article we will be using the TwitterAuth API with flutter and Express to demonstrate how you can use any platform for authentication with your Flutter app while having you own custom server (in Nodejs, Django, Express, Java etc).

Let's Get Started!

In this first article we will setup a Flutter project and connect it with our Twitter API.

START A FLUTTER PROJECT

flutter create letsauth

This command will create out flutter project that we will use to demonstrate for authentication.

START A FIREBASE PROJECT

Head over to firebase console and start a new project as shown below.

Fill in the details they are asking (you can disable Google Analytics) and you will have your project ready.

If all went well you will see a screen similar to the one shown above. Now it's time to connect our project with this flutter project.

Depending upon the platform you are currently on (I'm developing for Android) click on the icon shown and complete the steps they have described carefully. Once you are done you should have your flutter project connected to the firebase project.

It's time to get out twitter api access tokens and connect it to FlutterAuth so that we can use it to sign-in in our app.

CREATE A TWITTER API APP

This step requires you to have a twitter developer account. Head over to twitter developer page and create an account if you haven't already. While registering your app they may ask for a fallback url if you are using TwitterAuth. Head over to flutter_twitter and enter the fallback urls mentioned there (copy past doesn't seem to work. Type it out)

Once your app is registered you'll get the access key and token. Carefully save them as we will need it in future to connect firebase with twitter api.

CONNECT FIREBASE WITH TWITTER

Alright, for the next step we need to tell firebase about our twitter api and that we will be using it for authentication. Head over to the firebase console and open your project.

On the left panel select Authentication and click on Get Started. You should see the entire list of all the apis currently supported like shown below.

Currently all of them are disabled but we will enable the twitter api so that firebase can communicate with twitter.

Click on the edit symbol next to twitter and enter the api key and access token provided by twitter that I asked you to save carefully.

Upon completion you'll get a url similar to

https://demodev-dfb1f.firebaseapp.com/__/auth/handler

copy it, we will be telling our twitter api about this url now, so that it knows firebase will try to communicate with it.

Open the twitter developer console again and head over to your project that you created.

Under the twitter auth fallback urls add the url that firebase has provided and save it.

Now you are all set to make twitter auth requests from your flutter app through firebase.

Please note that you can follow the same steps to connect with potentially any auth api that firebase supports.

In this next article i will show you how you can make auth requests (to twitter or any api) from your flutter app.

Follow me so that you don't miss the next 2 articles regarding FirebaseAuth.

Thanks for reading,
Jha

3 Steps To Architect A Express Server

Amit jha — Wed, 13 Jan 2021 09:27:38 +0000

Hey there fellas! I'm back with another interesting article that will help you become a full-stack developer.

Let's get started!

A lot of young developers focus too much on making the code work than on the architecture of the project. However, when you work in large teams with potentially hundreds of people working on the same codebase it becomes important to understand and architect your projects so that it's easier for others to understand and maintain.

So in today's post, I'm going to explain a popular pattern with the help of nodejs express server.

NOTE: I'M ASSUMING YOU KNOW BASIC NODEJS

STEP 1: INSTALL DEPENDENCIES

Start a Nodejs project

npm init -y

The above step is going to create the package.json file that we need for a nodejs project. It stores all our dependencies that we will be installing.

Install nodemon

npm install nodemon --save

We basically need this package because we want the nodejs server to automatically restart when we make any changes while development. We will come back to nodemon in a later step.

Install express

npm install express --save

STEP 2: CREATE FILES AND FOLDERS

In this step, we will create all the skeleton files and folders for the server.

But before that lets modify the package.json file a bit.

Right now package.json looks like this

But we are going to add a script to use nodemon for auto-restart of the server while development.

"dev": "nodemon app.js"

We will create app.json soon which will house the starting scripts of the project.

Now we are ready to start creating files and folders.

app.js

Inside your project create a new file called app.js that will be the starting point for the server.

middleware folder

Create a folder in the project directory called middleware that will contain all the middleware your server is using (like auth).

model folder

create a folder in the project directory called model that will house all the files that will contain all the data models and will act as a point of contact with the database. No other part of the server will directly interact with the server but the files inside the model folder.

view folder

Create a folder in the project directory called view that will contain the business logic. Files inside views will interact with the models to get the data from the server.

controller folder

Create this folder in the project directory and remember that you will have all your route callbacks here.

route folder

Finally, create a route folder in the project directory that will contain all the routes in your server.

another way to go about this is by combining controllers and routes as suggested by Daniel Hillmann in the comments

In the end, the folder structure looks like this:

STEP 3:

Now for the sake of demonstration, we will set up an end to end route that will serve a request.

Let's get right into it!!

First, open app.js and type out (or paste) the code

const express = require("express");

const app = express();

app.use("/", require("./route/index"));

const PORT = 3000;

app.listen(PORT, () => {
    console.log(`listening on port: ${PORT}`) // use ` not '
})

line number 5 will forward all requests to the server to the index.js (we will create it) from where we will make calls to the controller.

Next, let's create the index.js file in route folder

const express = require("express");

const router = express.Router();

_hello = require("../controller/hello");

router.get("/hello", _hello.callback);

module.exports = router;

Line number 7 will call hello.callback for every request that is made to _localhost:3000/hello

Next up, let's create the controller callbacks.

Create a file in controller called hello.js and type out this code:

const helloView = require("../view/helloView");
// import your data model and use it 
// for your business logic
module.exports = {
    callback: (req, res, next) => {
        res.status(200).send("Hello There!");
    }
}

THAT'S IT!

now if you start the server by running the following command

npm run dev

you will be able to make a get request from your browser to localhost:3000/hello and see a message saying Hello There!.

In this post, I showed you how to structure your express server so that it's easier to maintain. If you found this post to be informative please consider following me and subscribing to my newsletter.

https://tinyletter.com/jha

Happy Learning,
Jha

How To Test Ionic React PWA On An Actual Device While Developing? YOU SHOULD!

Amit jha — Wed, 29 Apr 2020 19:20:37 +0000

As I spoke about the future of App development in one of my posts, I briefly touched PWA aka Hybrid applications and why you should learn it.

Now maybe you started learning how to develop PWA using Ionic but when you ran ionic serve in the terminal the app started in a browser tab. But you are developing it for smartphone users, right?

Hey, don't worry I'll explain how you can run it on an actual device WHILE developing it.

Let's go...

Step 1: Google it

Just kidding.

Connect your android device to your computer/laptop with a USB cable and turn on usb tethering
Open the terminal and run

ipconfig

Note your tethering hotspot IP address like the one in the below figure
Run ionic server to start the app

ionic serve

You can access the app through any phone browser at IP_ADDRESS:8100

Now you can test your app on your device while developing it. Any change you make to the app will be reflected in your device instantly.

Why you should?

Well, imagine your PWA has a QR code scanner. How will you test its functionality without loading it onto an actual device? This is one of the reasons I prefer testing PWAs directly on the device instead of a simulated browser instance.

That's all for today guys.

I'll see you in the next one.

Cheers,
Jha

Some of my previous posts that you may like

--save and --save-dev : Why You Should know The Difference

Amit jha ・ Apr 28 ・ 2 min read

#npm #javascript #devops #react

Why learn Docker

Amit jha ・ Apr 25 ・ 5 min read

#docker #webdev #devops #aws

Why I Prefer PyTorch Over TensorFlow: Same Reason I Prefer Linux Over Windows

Amit jha ・ Apr 28 ・ 1 min read

#machinelearning #deeplearning #python #pytorch

--save and --save-dev : Why You Should know The Difference

Amit jha — Tue, 28 Apr 2020 09:49:13 +0000

We all have been rooky at almost everything at some point in our life, being a developer has not been an exception.

As a newbie, we all make mistakes and overlook things because either they look simple or overly complex. While this ignorance does not cause any major embarrassment in our devlife (hopefully), sometimes somethings are worth paying attention to.

Like the difference between --save and --save-dev while installing package through NPM.

What do they do anyway?

Every node project has a file called package.json that contains the details about the packages installed in the current project directory and alias for commands to start, build the project. Other than that it also contains two json objects that are of our interest in this blog post. dependencies and dev-dependencies.

What are dependencies?

These are the packages that are required for the application to work properly. For example, You need react-dom to run a react project.

Then what are dev-dependencies?

These are the packages that you need while developing the project but not when deploying the project. These packages are not built when the project is deployed. Example: A package for instant-server for quick rerendering of a web page being developed.

What does --save and --save-dev do?

Well, You already know the answer now, don't you?

--save saves the name and version of the package being installed in the dependency object.

--save-dev saves the name and version of the package being installed in the dev-dependency object.

As developers who are just getting started or want to build an application that can be easily deployed without any problem this difference is a must know.

Or else this is how you'll find yourself

That's all in today post. I'll see you in the next one.

Cheers,
Jha

Some of my other posts that you may like

7 Tricks To Get More Done As A Developer

Amit jha ・ Apr 26 ・ 6 min read

#productivity #devops

Why learn Docker

Amit jha ・ Apr 25 ・ 5 min read

#docker #webdev #devops #aws

I also write on Medium

DEEP LEARNING: SERIES ANNOUNCEMENT - Amit jha - Medium

Amit jha ・ Apr 28, 2020 ・ 2 min read
Medium

Why I Prefer PyTorch Over TensorFlow: Same Reason I Prefer Linux Over Windows

Amit jha — Tue, 28 Apr 2020 08:31:38 +0000

Hey everyone as we kick start this series I would like to shed some light on why I prefer PyTorch over TensorFlow and why you should too.

As a deep learning practitioner I like (or require) custom architectures for my projects or research papers which can be difficult to build using TensorFlow because it’s implementation is not very friendly (non-pythonic). Hence, building a custom architecture in TensorFlow is time-consuming.

Additionally, unless you are using core TensorFlow you don’t have much control over anything other than the number of layers in a model and their configurations.

PyTorch, on the other hand, gives you complete control over how you want to train your model and what should be the underlying architecture. In fact, it uses OOP for building deep learning model and the training loop is an ACTUALLY python for loop!!

This gives you full control over how the model is trained and provides you with all the optimizations that libraries like TensorFlow provide.

Now that I’ve explained why I prefer PyTorch over TensorFlow we are ready to explore deep learning.

Cheers,
Jha

This series will also be available on Medium

DEEP LEARNING: SERIES ANNOUNCEMENT - Amit jha - Medium

Amit jha ・ Apr 28, 2020 ・ 2 min read
Medium

Some of my other blog posts that you may like

7 Tricks To Get More Done As A Developer

Amit jha ・ Apr 26 ・ 6 min read

#productivity #devops

Why learn Redux in 2020: A way to deal with react's messy state management

Amit jha ・ Apr 25 ・ 3 min read

#react #javascript #webdev #redux

7 Tricks To Get More Done As A Developer

Amit jha — Sun, 26 Apr 2020 14:46:26 +0000

You have been there, haven't you? You have had epic ideas in your head that could bring down FACEBOOK, make you the next Steve Wozniak? But you didn't do anything about it because you were too cooked for it.

You are lazy. Sliding your fingers on the keyboard and building something wonderful is a waste of your mental horsepower.

But you want to change, right?

You want to take down FACEBOOK or you want to make something more mature than a stupid social networking site that survives by selling your data.

Well, I'm here to help. In today's blog post I'm going to present to you 7 ways to turn your life around as a developer. The techniques are fully tested by professionals and many of them are part of my daily routine.

You can learn about them through self-help books but hey! who has time to read when you are busy building cool stuff?

Let's go...

1. Clear Your Room/Desk/House

What!! No way. That's the most useless thing to do. I'm done here. This post is useless.
Hang on buddy...
Cleaning your room has a psychological effect that makes you feel happy and positive immediately, at least to some extent.
Not just that you are moving your limbs (thank god) while cleaning, that means your brain is making decisions instead of procrastinating.

'Where should I throw this rotten banana peel?'

Nah mate, I'm not convinced.

sure, here is a link that may convince you.

Still not convinced? You can close this post. We are talking business here, this is not a pep talk.

2. Make A Journal

Actually, make 2.
One for your day planning and to-do list (To-Do Book) and another to write ideas and thoughts (Thought Book).

Do you already do that? Oh, you have tired but didn't work out? okay.

Try again. But this time try this:

Every morning open your journal and look at your long term goal and check where do you stand currently (ex: 23% achieved). This will give you perspective.
Then based upon your current standing start making entries in the to-do list.
Once you are done with that flip back to the previous day and copy the pending tasks.
Lastly, start writing the estimated time when you will do that task.

This entire process hardly takes 6/7 mins but it will have a huge impact on your productivity.

Why?

Because you are no longer worried about "what was I suppose to do next?". You have all that on paper.

But that's not it, make sure to carry it everywhere and keep checking it even when you know what task is next. This will help you stay focused.

Strike the task as soon as it is done. This will have a subconscious impact and make you feel better. YOU ARE IN MOTION!

One more thing. Don't hesitate to make changes. For example, one task took 1/2 hr more than you expected (it will always happen, trust me) then take 5 mins and adjust the estimated time for all upcoming tasks accordingly.

The idea of a to-do list is not to have a rigid schedule and get everything done, the idea is to get more done

Todo list has changed my life for the better and I'm sure it will change yours too.

Moving one to thought book.

Why do I need it? You do. We all do.

As much as you may deny it we are not conscious about our thoughts. The notion that thoughts are progressive, moving from one topic to another is wrong. Actually our brain is much more complex than that. Most of those thoughts that we have has been there even before you realise they existed. If they are positive GOOD. But if they are negative it will only affect your productivity. The best way to deal with it is to write it down. You don't have to read your thought book, it's just a psychological trick.

As soon as you catch yourself thinking instead to being productive, sit bolt straight (that's important) and write your current thought in the book. As time passes you will become more productive and think less crap.

It works, trust me.
ps: DON'T USE TODO APPS. USE PEN AND PAPER ONLY. IT'S NOT COOL BUT IT'S MORE EFFECTIVE.

3. Throw your phone away

Goddammit Charles, not literally...

Now, I know you are outraged but trust me your biggest distraction is your phone (FACEBOOK/WhatsApp/Instagram/Wechat etc). If you want to be a productive developer keep your phone as far as possible (ex. keep it in the hall while you work in the room). It will be hard in the beginning but eventually, you will get over the urge to check it.

If your work requires you to use your phone (App developer) then keep the data off or avoid using the social networking applications (hell just delete them bob).

Not just on your phone, try to avoid using social networking on your laptop/desktop. How? keep checking your todo list and look at the time to find out what you should be doing at the moment then FORCE yourself to do that.

Keep writing your thoughts.

4. Take breaks

Don't get so caught up while working that you forget to relax. Our brain (and eyes) need to rest after every few hours for better concentration, make sure they get that.

One neat trick is to drink a lot of water 😉

Also, make sure you check your todo list after every break to make sure you are on track. If you do not then modify the todo list. Be flexible.

5. Work out regularly

Regular workout keeps your body fit and your mind laser-sharp.
There is nothing much I have to say here. This is a no crap post. Workout, it's good.

Here are the things you should do at the bare minimum:

10 Jumping jacks
10 Inclined push-ups
10 wide push-ups
Run for 10 Mins
5 wide push-ups
5 Inclined push-ups
5 Jumping jacks

This will hardly take 25 mins of your time but you'll feel young, boomer.

6. Avoid caffeine

As much as you'll say otherwise caffeine is not good for you (in the long run). Make sure you don't consume it in any form. Replace it with more healthy options. Drink warm water. Green tea. The list goes on.

It helps you concentrate more? At what cost? Your health is more important than staying up until 4 AM to get something done.

And honestly, if you follow all the advice above then there won't be any need to stay up that late. You will be doing more than what you expected in record time.

7. Sleep at least 6hrs every day

Sleep is one of the most essential parts of our schedule. Sadly, as developers, we sacrifice it more frequently than we should. As I said earlier if you follow all the advice in this post you won't need to stay up late or drink coffee. Your life will change forever. Mine did.

That's all from me folks. Tell more about your productivity hacks in the comment section below. I would love to learn from you all.

Cheers,
Jha

Some of my other posts that you may like

Why learn Docker

Amit jha ・ Apr 25 ・ 5 min read

#docker #webdev #devops #aws

Why learn Redux in 2020: A way to deal with react's messy state management

Amit jha ・ Apr 25 ・ 3 min read

#react #javascript #webdev #redux

Why learn Docker

Amit jha — Sat, 25 Apr 2020 11:28:57 +0000

Let’s be honest, software development is hard. Especially when you are working on a product with separate components that are required to be integrated together. Over the years different software development techniques have been developed to streamline the development process and meet the requirements and quality at the same time. However, in recent years as cloud-based technologies have flourished, most of the existing development methods have become somewhat difficult to manage when it comes to developing quick and fast cloud-based software solutions. In today’s blog post we discuss why to learn docker and the technologies and processes that surround it.

Let’s get started…

What is the problem

To give you some context let’s say you are developing a product for a particular customer(a company or client) and you are using different technologies such as client database, static front end, back-end development, virtual machines, production cluster etc. You can see this is a heavy project. Now, imagine you need to upgrade the database server or say you want to switch from MySQL to MongoDB. Well, it doesn’t sound like a huge problem, right? To be honest, it’s not impossible but to be able to make this transition not just the database server but also all the features that are using the database have to be updated. This increases the amount of time required to complete the upgrade and the developers may end up inducing more bugs into the system. So the problem is scalability and software evolution.

Now, Imagine your customer doesn’t want you to set up your own in-house server for this product instead its suppose to be in the cloud. That means this entire product has to be able to work in a remote server(cloud). This gives rise to yet another problem. Now you have to manually install all the dependencies on to the remote server(cloud) before you can deploy the product. And every time a new version or a new feature is added to the product the dependencies in regards to the feature have to be installed onto the server. This gives rise to yet another problem. Now if a feature requires a certain version of the previously installed dependency the previous version has to be replaced with the version that’s required, but now the feature that was using the previously installed version has to be updated otherwise the system will not work as intended. As you can see this requires a lot of work from the developer just to deploy and improve a product. This slows down the development process as the developers have to make sure that the installed package is not broken and take care of the dependencies. So the problem is portability.

Now that you have understood what the problems are let’s try to find out the solution…

Solution

Okay, let’s try to find a fix to all the aforementioned problems.

Let’s get portability out of the way first. How do you make something portable? For example, if you have to shift to a new place you rent a container truck, load all your stuff into the truck and then transport it to where ever you want. Well, that’s the most logical thing to do, right? This is exactly how applications are deployed in a cloud-based architecture.

Container

A container is like a virtual box that has all the necessary dependencies installed for a particular product. It’s better than a native virtual box because it can run directly above the existing operating system instead of running an entire operating system over the existing one. A container runs as a process in the existing operating system such that the applications running under it are isolated from the system, that is, the application runs exactly as it is supposed to irrespective of the operating system. If it doesn’t sound like a big deal then have a look at this example. Imagine, Your application needs to run on a cloud server but the code and scripts and dependencies are installed on your local system. So now to deploy this product to a cloud server all the dependencies have to be manually configured in the remote server. But you have decided to try out this new technology called containerisation to deploy your application. So, you write your containerisation script to automatically configure your remote server with all the dependencies and automatically deploy the application for you. Not just that, because a container runs over the existing operating system as a process you can have multiple containers running on the same server without worrying about dependency conflicts we talked about earlier. How neat, right? Well, that’s exactly what a container is for. It raps up all the scripts and it’s dependencies into a container such that it will always run as intended irrespective of the operating system and environment.

Now, we understood how the portability problem is solved using containers but what about scalability? And software evolution?

Again, let’s understand this with the help of an example. As a developer at a cloud-based company, you successfully deployed a product which is now gaining traffic. Your company wants you to scale this product up. Meaning, increase its capacity to handle the traffic. In the case of a product deployed on the in-house server the entire server would have to be reconfigured(hardware/software-wise) but in a cloud-based architecture which is using a containerization service all you have to do it run multiple instances of your image, do some software configuration(load balancing etc) and you have successfully scaled up your product. It’s more complex than I’m making it sound but at a surface level this is what is happing. This solves the problem of scalability.

After you scale up the product you realise that the customer requirements have changed, meaning, some new features are supposed to replace the older ones(for example, make login more streamlined). Well, guess what you have to do? Develop a more streamlined method to login deploy it as a container in the cloud and use restful API to communicate with the service. See, your product just evolved based upon customer requirement. This solves the problem of software evolution. This is just one method to solve this problem. In fact, some of you might argue that this is not the right way to do it. I could agree with you but then this blog post is to explain the benefits of containers and docker in simple terms so I think it doesn’t need to be absolutely precise about the implementation of containers.

WHERE DOES DOCKER FIT INTO ALL THIS?

Because you are already reading this blog post I assume you already know what Docker is used for. However, if you are one of those people who came across this post by accident and have no clue what Docker is, well don’t worry its not another complex jargon you need to understand before you can dive into containerisation. Let me give you the internet description of Docker. It’s an open-source project which is used to write container images that can be easily deployed on the vast array of web service providers.

So now that you understand why containerisation and Docker are so important for the current industry you are ready to go out and explore it on your own. Thanks for reading today’s blog post. I’ll see you next time. 😉

Cheers!
Jha

Why learn Redux in 2020: A way to deal with react's messy state management

Amit jha — Sat, 25 Apr 2020 11:08:40 +0000

Let's be honest, react's state management is a nightmare for everyone working on large and small projects alike. The tree like structure that react brings to the table is sure worth it but the state management causes more pain than pleasure.

How? let me explain it

The story of a smart developer

Arther and Susan are the frontend developers at HavenLabs. A state-of-the-art research and product development lab. Arther and Susan want to make it big in this company and therefore put in the work to prove themselves. However, due to the recent market crunch, the company can only afford one frontend developer. So, in order to decide who is better, the company decides to give them a task and see who deserves to be kept.

Now, this is where things get interesting.
Arther decides to use react's state management and Susan decides to use Redux. They are given 1 week time to finish the project and both finish it on time.

Hmm, the manager is confused now. They both have completed the project on time and both applications are working fine. To further assess both to them the manager changes the requirements of the application. These new requirements need some modification to certain parts of the application and the deadline is tomorrow.

No problem both of them get to work right away.

The morning of judgement is here and they have to present their applications. Susan presents what she has built and also explains the structure of the project to the manager. The application is working exactly as expected. She is confident that she will be the one who won't lose the job. On the other hand, Arther looks tired and dull (because he was developing the application all night). Nevertheless, he presents his project and just to impress his manager he decides to show off a working demo but as soon as he clicks on a button an error pops up

props.getInputValue("order") is not a function

OOPS!
Looks like Arther forgot to pass the props down to the child component.

The manager is not impressed and Arther loses his job.

Moral of the story: Don't use react's state management

Why?

Why learn Redux in 2020

There are several reasons to consider redux but I'm going to list the most intuitive ones and provided links for people who want to learn it.

Redux brings the concept of sing source of truth to the table. Instead of passing props from the parent component to children or lifting the state up, redux stores all the states at one place called the store. This store is accessible from all the components in the application and a component can receive and modify props from this store directly without expecting the parent to explicitly assign the props. React states messy no more.
Redux brings structure to the project and overall the code-base becomes much more readable and clean.

That's all folks for today! I hope you enjoyed reading this post. If you did please click on the ❤️ button.

See you in the next one
Cheers,
Jha

A great post to learn more about redux:

Should You Learn Redux?

Steven Mercatante ・ Nov 7 '19

#redux #react #javascript #webdev

Additionally,
Redux for beginners

Some of my previous posts:

The future of App development

Amit jha ・ Apr 23 '20

#javascript #react #pwa #flutter

Deep Learning through first principle: 01

Amit jha ・ Apr 24 '20

#datascience #machinelearning #python

Deep Learning through first principle: 01

Amit jha — Fri, 24 Apr 2020 08:54:10 +0000

Machine learning has truly captured the attention of the big and small alike. The adaption has reached such a state that there is a lack of deep learning experts in the industry. In this scenario, it becomes important for every deep learning practitioners to not just learn to "build" deep learning models but also learn about them through first principle. In this series, we will break down the deep learning development cycle and write them in PyTorch.

But today, let's talk about deep learning in general and try to understand it with an example. Let's go...

Let's try to connect the neural network(NN) with our life. Imagine, you are a neuron in a vast network. The decisions you make are directly or indirectly affected by every other neuron in the network(other people). You may argue that a kid living in a remote place on earth would never affect your life in any way, which is true. But in that case, the effect of that child's actions(or existence) would be infinitely small and therefore nonexistent. However, that does not mean the kid is not a part of this network. We all are.
Similarly, your actions affect everyone's life. The people you know and the people you don't. Interestingly, this concept is not limited to humans. Everything in existence--dead, alive or lifeless--is part of this network. In this way, we can propose that the entire world is nothing but a vast neural matrix that functions as though it is one.

Your action A is the cause of someone's(or something's) influence W and your experience E towards a known or unknown goal G.

In this series, we will be diving into all these variables and discussing in greater detail about what else triggers and affects A, where does E come from, what is the concept of W and most importantly what is G.

Make sure you follow me and save this post because I will be updating the index here as I add newer content.

Also, hit the ❤️ button if you liked this post

Cheers,
Jha

The future of App development

Amit jha — Thu, 23 Apr 2020 14:52:29 +0000

In the last few years, native app development has seen a shift from the 'native' tech stack to a more 'web' oriented development stack. While one can easily read articles and find loads of reason for this I think one the fundamental level there is only 1 reason for this shift: the need for One-to-many application. In this post, we will be diving into this reason to understand what it is.

The need for one-to-many Application

Huh?
Okay fine. One-to-many application is just my way of saying one code base and support for all platforms (Android/iOS). But what is it anyway?
These applications are written once and supports both android and iOS out of the box. No need to rewrite anything separately for any platform. Well, is there anything even remotely similar to that? YES!

Here are a few of them:

Flutter
React-Native
PWA

Let's look into what these are.

Flutter

It is a framework developed by a team at Google for building fast and responsive mobile applications. It can be deployed to both Android and iOS without you having to rewrite the entire application for a specific platform.
Pros:

Easy to learn
lightning-fast development lifecycle
Compiles to native code
Fast and responsive
Growing community
Easy to connect to native APIs even if they are not directly supported Out of the box support for many Google services

Cons:

Requires you to learn dart
Many native APIs not supported. Hence may require knowledge of native development cycle to interface it with those APIs

React-Native

It is an extension to the popular front-end development framework React to develop fully functional and responsive mobile applications with web technologies alone. All you need is experience with HTML, CSS, JavaScript, JSX and you are good to go. If you haven't heard about react or react-native then you should definitely check them out.
Pros:

The only knowledge you need is Webdev

Supports many of the APIs supported by react

Amazing community online to help you out

Cons:

Flutter has a much more stable development life cycle even though react-native is more widely used

PWA (Progressive Web Application)

> Hey, What is PWA?
>> Progressive Web Application
> Aren't all applications progressive
>> d.e.a.d

Lame joke, sorry :P

What are they actually? Well, it is something which is truly one-to-many application. Have you ever visited a website and received an annoying popup asking you to add the app to your home screen? You have. Exactly.

These applications run in the browser and can be installed in the device as an application. To be honest, install isn't the right word to use in this case but for the sake of argument, we will accept it. So, you write one application for the browser and that's it. Your application can be accessed from anywhere in the world on any platform and not just that, you can even install an instance of that application in your device that feels and works like a native application. Isn't it cool?

PWA is a relatively new concept and it can be a game-changer in the long run. If you have not started learning PWAs development cycle then you are seriously missing out. One such framework for PWAs is Ionic. Do check it out.

Additionally, these frameworks discussed above also help companies save money because now they don't have to divide their teams to work on iOS and Android separately.

Furthermore there are several more reasons to consider PWAs and such technologies and I hope this post makes you curious enough to explore them.

Cheers,
Jha

DEV Community: Amit jha

(1/3) Nodejs With FirebaseAuth: The Right Way

PART 1/3

Let's Get Started!

START A FLUTTER PROJECT

START A FIREBASE PROJECT

CREATE A TWITTER API APP

CONNECT FIREBASE WITH TWITTER

3 Steps To Architect A Express Server

Hey there fellas! I'm back with another interesting article that will help you become a full-stack developer.

STEP 1: INSTALL DEPENDENCIES

Start a Nodejs project

Install nodemon

Install express

Now we are ready to start creating files and folders.

app.js

middleware folder

model folder

view folder

controller folder

route folder

STEP 3:

How To Test Ionic React PWA On An Actual Device While Developing? YOU SHOULD!

Step 1: Google it

Why you should?

Some of my previous posts that you may like

--save and --save-dev : Why You Should know The Difference

Amit jha ・ Apr 28 ・ 2 min read

Why learn Docker

Amit jha ・ Apr 25 ・ 5 min read

Why I Prefer PyTorch Over TensorFlow: Same Reason I Prefer Linux Over Windows

Amit jha ・ Apr 28 ・ 1 min read

--save and --save-dev : Why You Should know The Difference

What do they do anyway?

What are dependencies?

Then what are dev-dependencies?

What does --save and --save-dev do?

Some of my other posts that you may like

7 Tricks To Get More Done As A Developer

Amit jha ・ Apr 26 ・ 6 min read

Why learn Docker

Amit jha ・ Apr 25 ・ 5 min read

I also write on Medium

DEEP LEARNING: SERIES ANNOUNCEMENT - Amit jha - Medium

Amit jha ・ Apr 28, 2020 ・ 2 min read Medium

Why I Prefer PyTorch Over TensorFlow: Same Reason I Prefer Linux Over Windows

Hey everyone as we kick start this series I would like to shed some light on why I prefer PyTorch over TensorFlow and why you should too.

This series will also be available on Medium

DEEP LEARNING: SERIES ANNOUNCEMENT - Amit jha - Medium

Amit jha ・ Apr 28, 2020 ・ 2 min read Medium

Some of my other blog posts that you may like

7 Tricks To Get More Done As A Developer

Amit jha ・ Apr 26 ・ 6 min read

Why learn Redux in 2020: A way to deal with react's messy state management

Amit jha ・ Apr 25 ・ 3 min read

7 Tricks To Get More Done As A Developer

1. Clear Your Room/Desk/House

2. Make A Journal

3. Throw your phone away

4. Take breaks

5. Work out regularly

6. Avoid caffeine

7. Sleep at least 6hrs every day

Why learn Docker

Amit jha ・ Apr 25 ・ 5 min read

Why learn Redux in 2020: A way to deal with react's messy state management

Amit jha ・ Apr 25 ・ 3 min read

Why learn Docker

What is the problem

Solution

WHERE DOES DOCKER FIT INTO ALL THIS?

Why learn Redux in 2020: A way to deal with react's messy state management

The story of a smart developer

Why?

Why learn Redux in 2020

Should You Learn Redux?

Steven Mercatante ・ Nov 7 '19

The future of App development

Amit jha ・ Apr 23 '20

Deep Learning through first principle: 01

Amit jha ・ Apr 28, 2020 ・ 2 min read
Medium

Amit jha ・ Apr 28, 2020 ・ 2 min read
Medium