I have made a simple Android app with Flutter, that sends data to Firestore. Now, I need to build a dashboard that will be able to view the data. Excel doesn't work, I tried Zapier but it seems too limited, and I gave a look at Retool , but it seems to only work with RealTime database, not Firestore yet.
Would you guys be able to recommend something ?
Zapier does the job. I just had to name every row accordingly to the fields from firestore
Chartbrew.com supports connections to Firestore. You can run queries using Firestore operations and generate charts and tables to explore the data.
Related
I have been reading a bit about Firestore and having a global Firebase Project, I'm of course interested in using Firestore.
Reading this firebase vs firestore page, at the bottom they say we can use both within the same App...
Well, that would be cool but wait...
What about Authentication?
Data Structure being different?
Storage?
With things being different between the two, how is it possible to use both at the same time within the same App?
I can't really picture it.
Cheers
Yes you can.
Actually each module have his method :
firebase.database() for database
firebase.firestore() for firestore
firebase.auth() for authentication
Etc...
And yes, database and firestore have different data structure
so I've finished making a full fledged Android application with which I store data and retrieve on Firebase Database.
However, since there are many joining statements (By using orderByChild and equalTo), the main home screen is very laggy.
The main reason why I'm using Firebase, is because it is a real-time database, however, there is only one screen where that is useful.
Do you think that it's a good idea to keep most of the data on an SQL database and only the data that requires real-time data transfers on Firebase, and will using SQL databases reduce the time it takes to load my home screen?
If you have a SQL background and you want to rewrite your application to use only Firebase, to have a better understanding, please take a look at this tutorial, The Firebase Database For SQL Developers. I asure you, Firebase will handle all your needs.
If don't have time to do this, than use Firebase just for the single activity that you need. If you think that in the future you'll need to make more than one section of your app to use Firebase, than think to change the whole app to use only Firebase.
Hope it helps.
I am building a mobile app to allow for real time messaging, befriending users, creating groups to both chat and share images with, as well as creating events where users can invite one another.
I have chosen to use Firebase as the online back-end. But, given Firebase uses a NoSQL data model, while Android SQLite uses SQL, when saving data offline in Android what is the conventional way to handle this? Is there a simple way to convert or simply save from NoSQL to SQL, or do I need to build a converter?
(This is especially important for the events, as once created, they must be scheduled in the AlamManager, giving users alerts upon event time)
While you could implement your own solution, truth is, you do not need to build anything from scratch.
There are free Android libraries which could help you. I would recommend you:
SimpleNoSQL
The transition from Firebase to SimpleNoSQL is pretty straight forward, and is mostly the same as if you were using any form of SQL:
1) You get the data from your remote db: you can get this trough a request to your remote server, it doesn't matter what language you are using as long as it can return a response you can catch.
2) You save said data to your local NoSQL db: once you have the information requested, it is up to you what to do with it. You could save it to a TXT file, a SQLite db, NoSQL db, save it to the SharedPreferences, etc.
Hope that helps.
I'm using Parse for the first time to play around with.
I use Realm.io as a offline db.
Both are very powerful and it's great to get to know them better.
(Big up to both teams!)
My app should be able to be used on remote locations, where you can't get data from Parse. I want to be able to rely on Realm in these situations.
I just implemented user management in Parse, but I don't know what would be the best way to reflect this with realm. Should I create a User object in realm and make a one to one relation with all my models. Should I save the username as a property in the models?
I also tried the combination of Realm and Parse. And yes you'll have to sync the data manually between both datasets by creating models for each.
But I think writing (almost) the same model classes for both Parse and Realm could be counter-productive. That's why I dropped Realm and used Parse LocalDataStore instead. By using localDataStore, you still would have to write the sync logic yourself but the code would be cleaner (in my opinion).
Another option is to go for Firebase. Firebase handles the sync logic itself so you don't have to and it even gives you real-time sync. So I would highly recommend you check that out. But Firebase doesn't have Push Notifications. For that you can still use Parse.
Hope this helps.
Update
Firebase now offers push notifications as well. (and Parse has been discontinued)
I recently started using Kinvey as a backend for my Android app. The documentation doesn't have a lot of info about Collections. I want to know if it's possible to create Collections using the same concepts applied to MySQL tables for example:
A Collection called Users will hold a User ID, Username, User Email
And another Collection called Items corresponding to users -> Item ID, Item Name, User ID.
Has anyone successfully created Collections like this using Kinvey?
kinvey.com
I have also contacted their support team about this bu no reply yet.
I'm an engineer at Kinvey and can help you at this. Kinvey uses a NoSQL store on the back end, so the concepts are a little different than those of a relational database system like MySql, but in general the same thought process can apply. A Collection is similar to a table, although it is Schema-less. This means that attributes (columns in MySql terms) can be added dynamically as needed. You simply create the collection, and then start saving data objects to it. For more info on our Android library specifically, take a look at our Data Store User Guide.