{"id":99,"date":"2016-09-02T18:18:19","date_gmt":"2016-09-02T12:48:19","guid":{"rendered":"http:\/\/codecrunch.co\/blog\/?p=99"},"modified":"2016-09-05T14:54:44","modified_gmt":"2016-09-05T09:24:44","slug":"diegesis-of-firebase-where-does-it-fits-for-you","status":"publish","type":"post","link":"https:\/\/codecrunch.co\/blog\/diegesis-of-firebase-where-does-it-fits-for-you\/","title":{"rendered":"Diegesis of Firebase – where does it fits for you ?"},"content":{"rendered":"

For many of us, mobile became a day-to-day life aspect, so natural that sometimes it\u2019s easy to forget how it actually works. So let\u2019s do a quick recap.<\/p>\n

Nowadays, mobile doesn\u2019t exist without a backend. That\u2019s pretty much a fact.<\/p>\n

Sure, you can point at some applications which are backendless, but these are a minority. Even if you would like to create a simple implementation of tick-tack-toe game, you would probably still require a backend to provide your app with some multiplayer gameplay feature or a board for your scores.<\/p>\n

So let\u2019s be honest \u2013 it is really important. More than that, a dedicated backend, created specifically for your mobile application is a real treasure for every mobile developer. But what if for some reason you can\u2019t have it?<\/p>\n

Firebase<\/a> provides a full set of authentication options out-of-the-box. Firebase automatically stores your users\u2019 credentials securely (using bcrypt<\/a>) and redundantly (with replication and daily off-site backups). This separates sensitive user credentials from your application data, and lets you focus on the user interface and experience for your app.<\/p>\n

#1 – The\u00a0Evolution<\/h3>\n

Firebase evolved from Envolve, a prior startup founded by Tamplin and Lee in 2011. Envolve provided developers an API that let them integrate online chat into their websites.<\/p>\n

Eventually over the run firebase was acquired by Google and as we all know well how android has evolved out of the box after google took matter in their hand, there was never a doubt on firebase future or was there?<\/p>\n

#2 – And there was a “PARSE”<\/h3>\n

At the time of introduction of firebase, there was already a tough competition in market from Parse<\/a>. Parse having an edge over firebase on many ground was a no match, in terms of verity of services available, a fully grown community support and most importantly number of active developers using\u00a0technology. Compared to Parse firebase tried to be nemesis which it never truly became.<\/p>\n

But as it always happens -the unpredicted future,\u00a0Parse<\/b> used to be one of the most popular mobile backend services. Unfortunately, on 28th January 2016 Facebook announced that they\u2019re\u00a0shutting down their product<\/a>.<\/p>\n

#3 – Fire from the base<\/h3>\n

The new Firebase<\/a> announcements made at Google I\/O 2016 really transformed\u00a0Firebase\u00a0and merged it seamlessly to\u00a0Google ecosystem and making it best in business BaaS (Backend as a Service).\u00a0Firebase now has best\u00a0of Google’s offerings and packaging it into a clean and easy-to-use package.<\/p>\n

 <\/p>\n

\"firebase_features_codecrunch\"<\/p>\n

#4 – What for you?<\/h3>\n

As a developer firebase now not only provides real time database and authantication but not it packs a punch with tons of new features, combining all major development products in a single package.<\/p>\n

list of the features:<\/h4>\n