Oh. Right. I was over-thinking this. A url to an image is something we can just use as the value of a Picture component. Or, yes, upload it to Cloudinary.
see, that i didn’t know. i assumed because it was an api, that it had to go into the api block and have the return value as the image, but i guess this would make 1000x more sense because its html… geeez… I’m a goofball, its like when you’re looking for food in the pantry and you keep looking, and cant find it.
then someone else walks up and grabs it right away, and it was right in front of you, lol
That’s a whole lot easier. I’ll update the project link ahead but here’s a simplified version. It’s basically the same thing @drted shared.
yea, that’s… i feel like an idiot, lol…
also, i figured out that, when you want to add a new user account storage to the Real-time database, all you need to when they sign up is set the key to their new user id, and then make an object or list of the values email, vin, uuid, job history, etc… jeez, i expect things to be way harder to use than they actually turn out to be…
App development is full of experiences like this. You spend hours debugging some small feature and then realize that there’s a way to do the same thing in a tenth of the time. But it’s all learning, right?
oh, heck yea!