We have a client interested in our app, which relies on Firebase. However, they want to use this while they are out to sea and won't be able to connect to the cloud.
They do have a local server and a local wi-fi network.
Does anyone know if using the Firebase Local Emulator Suite would be a practical solution to this problem?
The Firebase Emulator Suite is for development, not sure production use. From its documentation:
The Firebase Local Emulator Suite is a set of advanced tools for developers looking to build and test apps locally
So it is (currently at least) not suitable for using in the scenario you describe.
What you can do is look at the offline mode of the various Firebase products, to see if they fit your needs. I recommend checking the documentation for each, or this handy video that covers all of them: Firebase offline: What works, what doesn't, and what you need to know.
Related
When I run my app locally, it's nice and fast, however, when I deploy to Vercel, things get very very slow. My app is a NextJS app, using Prisma as the db client. The database is an Amazon RDS Postgres instance. I'm pre-launch so there's no real traffic, so I don't think there are issues with connections or that I need a pgbouncer setup... though I don't really know how to audit that either.
Any tips I'd love to hear em!
Might be worthwhile to use the browser Dev Tools, specifically the Network and Performance tabs, to see if you can find what is slowing you down.
You could also check out using the React Dev Tools and look at the Profiler tool there, but that has to be run locally, which may not be as useful, since you say the app runs fast locally
Basically I've finished my beta React Native app, and I'm ready to test it with a private group of people, in order to know if it's stable and to correct possible bugs.
I am using firebase as a backend, so I am wondering if it's better to Firebase Test Lab and/or Firebase App Distribution or TestFlight (for the IOS).
I would like to know the advantages of this tools.
https://appcenter.ms/ is pretty decent (Android)
for iOS you might want to use TestFlight (you need apple developer account
Firebase Test Lab is not for app distribution. It is a way to determine if your app has quality issues prior to launch across a wide variety of devices.
I haven't had much success searching for this. I'm developing an Android Things application that will connect to a user phone to do certain things. I want to use this for delivering app updates as well.
So far, my crude searches on this have just discussed OTA via the Console and thus internet.
My gut has said that I could just build this - I could have a new version of the APK, transfer it to my device via bluetooth, and then just have the device copy it over the old one and reboot. But, not sure. I was hoping maybe there was an API for this and I'm just not wise enough to know how to find it via the searches.
We are experimenting with test automation and have found that cucumber-jvm/espresso fits the best. Our next issue is finding a testing service that supports the framework. To run the tests we are currently running 'gradlew connectedCheck' at the command line but from what I have read, AWS Device Farm doesn't support cucumber-jvm/espresso. Any service should work, so long as it supports cucumber-jvm and has a variety of physical devices to test on.
I am hoping that someone out here has experience with this and knows where we should look.
Thanks
Is it necessary to use Cucumber along with Espresso in that case? You can always implement an entire test suite without the need of Cucumber. All you need is a good reporting tool to report you the passes and failures. There are plenty of solutions out there -- I would recommend using something like Spoon or Composer to run your tests in parallel on multiple devices or emulators or a combination of both. Both of these tools provide decent reporting. As far as a device farm is considered, AWS will support that.
I am trying to connect my tessel to firebase, and I have tried everything. Is anyone else having a similar problem? I have read that the tessel uses different web sockets than firebase, but I am really new and don't know much about that. Could anyone help me out?
Glad to hear that people are interested in using Firebase with the Tessel. I'm one of the Firebase engineers who has been working with the Tessel folks to make this happen. There are two Tessel Forum posts that give some more detail on the problem:
Firebase cannot be compiled by Colony
Websockets on Tessel
The Firebase node packages uses faye-websockets, which the Tessel compiler couldn't support. We got nodejs-websockets to compile, and built a version of the Firebase library to test the concept. I was able to read and write from Firebase using the Tessel, but we were very hesitant to release a separate version of Firebase to NPM just for use on the Tessel, especially since nodejs-websockets is not as well maintained as faye-websockets. I then spent an evening working with the Tessel folks to get faye-websockets working, and it now compiles, with the changes sitting out on a branch (tessel/runtime/JH-HTTPParser). I don't have a timeframe on these getting merged into Master and being shipped out to production, but I know there are a good number of SSL and websocket based API's who are waiting on these changes to hit the main branch.
TL;DR: Firebase compiles on the Tessel (you can build the code off the above branch), and it can either read or write (not both at the same time). When I get some more time, I will be debugging Tessel + Firebase to get this working correctly.
With the acquisition I haven't had much time to try. Last time I checked, things were compiling and running for some operations (I haven't tested everything) if we used a non-minified version of the Firebase library (not currently provided to end users). The issue here is that the minification puts all the variables in the same line, and the Tessel Lua VM would complain that there were more than 200 variables and wouldn't like it. I can play around with it some over the next week and see where things are, otherwise I can ping Jon and the Tessel folks to see how we can best move this issue along.
I am using SynergyKit for realtime communication. You can download Node.js library, which is fully supported by tessel platform and using websocket library, which is one of few libraries written in pure javascript.
You will be able to live observing all data in collections and sending messages. There is documentation for Node.js.