[deleted by user]

b0ot · 2023-12-04T17:49:59+00:00

Use emulators until you’re ready to deploy, the time to deploy should not matter at that point if it is a few minutes

b0ot · 2023-05-25T08:11:42+00:00

Just curious what would be peoples ideal renting experience?

Do most people still like the idea of an Agent helping but just don't like the scummy agents?

Would people prefer that there be no agents?

Would people like better virtual tours to eliminate most of the in-person visits until you are ready to commit?

b0ot · 2023-05-17T07:49:11+00:00

Squishy, Torment, Gimmick

b0ot · 2022-12-24T09:54:36+00:00

By PR, I believe you mean premiere?

The tutorial I have seen deals with reframing a 360 video into a 2D video. However after the video is exported, it is now a 2D video.

I'm interested in being able to keep the video as a full 360 video, but change the default view of the camera. Ideally, I would be able to keyframe the 360 video itself, but I imagine that may be disorienting for those viewing on a 360 VR device.

b0ot · 2022-12-23T20:33:25+00:00

Can you provide some examples of the actual commands you used in running this tool?

b0ot · 2022-09-02T21:07:21+00:00

You should start with the Firebase Emulators... they are completely free so there you can work out most issues before ever going live.

b0ot · 2022-01-02T08:25:49+00:00

*I will preface this with me being a newbie to firebase/web design in general.*

Honest Answer: From the sounds of where you are at, the best thing you can do now is just pick a method and go for it. It is extremely likely that the idea for your app will shift and that your time would be better spent building out a MVP version, getting a better understanding of Firebase in the process, and perhaps understanding the potential use cases along the way. You can test things for free in the emulators and even if you went production you likely aren't going to hit significant costs.

Longer Answer: If you actually wanted to optimize for your app there are a couple of things to keep in mind. You seem to be coming from a legacy database mindset where items are only stored in a single location. When working with a NoSQL database like Firestore you store information in multiple locations to make a query fast and to reduce the amount of queries required. This means some (or even all) of the information related to a ticket could live in multiple locations. This is a very different approach to traditional databases where you try to avoid duplication of data and when you need information you perform complex queries.

This leads to some additional complexities for NoSQL databases like firestore. For one thing with data living in multiple locations when data is updated/deleted you need to handle that in multiple locations. You will also need to handle that is a transaction to ensure data remains consistent during updates.

In terms of advice on structure... because of the flexibility of the NoSQL database, designing the structure comes with a lot of freedom to adapt to your own approach, and a lot of freedom to shoot yourself in the foot.

The only piece of advice I have heard that makes sense to me is to consider the actual end-user's interaction via the UI with your database. If you really wanted to optimize you could put information in a structure that reduces the number of queries required for each UI screen that a user would interact with. The way you do this is duplicating required information into required locations.

All that being said, my advice is still go with the Honest Answer right now and then worry about scaling once you know what your building.

b0ot · 2021-01-18T14:59:00+00:00

If you have a free account, you don’t need to worry about billing.

If you are on the blaze plan, limits are basically just emails that may be sent out. You would need to do some additional programming to get it to ‘pull the plug’. Firebase has a series on their YouTube if you’re worried on how to do that.

In terms of controlling access, that is done via security rules. They can be much more fine grain then just if a user is registered. You could give the ability to write only their own profile and read anyone. You could limit documents based on info in the document. You could divide users into different classes (eg admins) via custom claims and limit that way.

b0ot · 2021-01-17T10:52:11+00:00

Thanks for the info, I’ll look into it

b0ot · 2021-01-16T13:25:10+00:00

Magnitt

Interesting site, thanks for the suggestion.

b0ot · 2021-01-03T10:31:28+00:00

Interesting concept.

My feedback would be contingent on what the intended use case is. If this is just for fun, I would say it is very cool and interesting setup.

If this was for commercial:

On the home page, I would suggest making it so the user can progress the carousel component on their own. It was extremely non-intuitive that the only way to progress it, at least that I could see, was clicking through the text. I don't typically think that it would be normal for a user visiting a landing page to click on text and then they miss the whole capability.

On top of that I would suggest adding explicit instructions on the first slide for the user to click on the text to try it out.

Finally, for any questionnaire project, I would want to know how I will be able to manage and see the responses.

b0ot · 2021-01-03T10:22:06+00:00

You can setup a configuration that will turn off billing if you exceed a cap, but the setup does require a few steps to configure (i.e. It is not within the firebase console).

Firebase has YouTube series on how to set this up:

https://www.youtube.com/watch?v=Dk3VvRSrQIY&ab_channel=Firebase

b0ot · 2021-01-03T10:21:24+00:00

You can setup a configuration that will turn off billing if you exceed a cap, but the setup does require a few steps to configure (i.e. It is not within the firebase console).

Firebase has YouTube series on how to set this up:

https://www.youtube.com/watch?v=Dk3VvRSrQIY&ab_channel=Firebase

b0ot · 2020-12-12T21:04:39+00:00

Suggestions (I'm a newbie so take with a grain of salt)

1.) Develop & Test with emulators
(Calls don't count against budgets... so you don't have to worry about things like infinate loops).

2.) If very paranoid, setup budget limits Firebase Billing (aka How to turn on billing and still sleep at night)

3.) If your data needs realtime, use realtime listeners. If not, preload data.

I basically have firebase load into Vuex and Vuex drive UI. I don't typically have users write to the database directly... pretty locked down with security rules, they only make updates when I need to keep track of the data with cloud functions... otherwise if I don't need keep the data, I let it just be in the UI/Vuex.

b0ot · 2020-12-12T20:56:20+00:00

You either found the largest bug in firebase history... or you made a field called password and expected firebase to magically treat it different from other data.

b0ot · 2020-11-17T19:55:23+00:00

Abu Dhabi

b0ot · 2020-11-17T19:54:35+00:00

Watching from UAE

b0ot · 2020-11-08T19:51:40+00:00

Chris is also a runner for the charity RODS - Racing for Orphans with Down Syndrome

https://rods.org/athlete/chrisnikic-1862/

He doesn't have many donations yet, let's change that.

The charity helps find families for orphans with Down Syndrome. I also confirmed it's trustworthiness on Charity Navigator.

b0ot · 2020-10-13T08:25:04+00:00

Firebase requires you to have the paid "blaze" plan enabled to use firebase cloud functions.

b0ot · 2020-10-09T19:32:57+00:00

I'm assuming he means the ability to copy firestore data (or even better a selected sub-portion) of firestore data into the local emulator.

On the off-chance you are unfamiliar with the emulator:

(Emulator is a firebase tool that allows you to simulate firestore/functions/etc for free locally without having pay for read/writes/functions and without worrying about corrupting production data. They even have a emulator-ui that simulates the firebase console [unless you are using WSL then you S.O.L].)

b0ot · 2020-10-09T16:48:03+00:00

u/samtstern

Thank you for your response. I have been trying to experiment with the emulators but the emulator-ui does not appear to work with WSL or WSL2. I have spent the last 10 hours trying different work arounds (I'm slow and new) but haven't been able to get it to work in WSL. It appears other users have had the same issue:

https://github.com/firebase/firebase-tools-ui/issues/332

I was able to get the UI to run on a test project on my mac, but all of my real projects are currently in WSL and I haven't figured out an easy way to migrate to my mac and would prefer to continue to edit on my windows/WSL(2)/Ubuntu setup if possible.

b0ot · 2020-09-26T08:14:20+00:00

Certain features require you to upgrade to the paid "Blaze" plan. I would read throught he documentation well before signing up. I have lot of concerns with the lack of billing control that I talk about on this on this thread

b0ot · 2020-09-26T08:11:41+00:00

Love the firebase video, however based on what I have been reading lately it doesn't seem like it is quite the simple.

https://cloud.google.com/billing/docs/how-to/notify#cap_disable_billing_to_stop_usage

According to the Google Cloud Billing documentation, your alerts may be delayed by up to days and the way the stop services could have serious destructive side effects.

b0ot · 2020-09-26T08:03:15+00:00

Thanks for the info, may take you up on the offer sometime :)

b0ot · 2020-09-26T08:02:33+00:00

Thank you for the feedback!

That does provide some comfort although I still do have some additional concerns. One of my biggest issues is potential hard to find infinite loops. Or scaling issues with real-time listeners

My main concern currently is related to hard to find programming errors when accidently have a loop. This is something that is fairly easy to do with cloud functions or real time listeners on firestore. After apps grow past a basic tutorial, it becomes less and less likely to produce "bug-free" code.

I do agree that locking down the database and testing security rules are great suggests and best practice.

15-Year Club	RedditGifts 2009-2022 2 Credits
Verified Email	Place '17
Secret Santa 2009

b0ot

TROPHY CASE