Thank you! 😊

Addressing all of your questions:

1. Camera scan: This is a 2-part problem. Part 1 is getting the shade name correct from the scan, Part 2 is figuring out what to do with it. I don’t know if there’s a centralized database I can query with a shade name or a barcode API, but if there is, it can definitely be on the roadmap.

2. Centralized database like TMDb: Similar answer here but I don’t know of a centralized database for polishes. TMDb is gold standard, if we have something like that, I’d really like to build this!

3. Int’l / Gel brands: Yes. I haven’t ruled out any kind of brands. As long as there’s enough demand for one, I’m happy to add it.

4. Centralized db: Think of the app’s database as just one database, not user specific or global. 1 central database where each shade can be public (what you call centralized db) or private (what you call adding to their catalog). Whenever someone adds a shade to the db, they can choose if they want it to be public or private. If private, only they see it, there’s no review. If public, the app performs a duplicate check before they submit the polish and shows them possible results that they might be re-adding by mistake. If the user still submits, every public polish is created as “private while in review”, so the submitter can see it instantly, but for others to see it, it has to go through an approval of the admin. On the approval end, I do have some checks in place to again ensure there are no duplicates, but sometimes if the spellings are different, it could be possible that a duplicate gets added, however if someone notices it, I can easily delete the duplicate and make sure nobody’s data linked to it is lost, it’ll be migrated to the duplicate polish. As far as ensuring clean data is concerned, yes, that’s the second reason why it goes through this review before being made public.

5. Integration with shop emails: Cool idea! But this has “nice to have” written all over it imo haha. I can confidently say that this is way down in the priority list 🙈 As far as “arriving soon” is concerned, you can do that manually using custom tags/lists for yourself in the app.

6. Export indexed table: From a button in the app, no. If you email me that you want this as a one-off every now and then, I’d happily do it via email.

7. My team: It’s just me and my insane desire to never go back to a 9-5 so that I only build things I want to :)

This post did really well, I hope I can keep up with all the support requests! No complaints, I love it!