@emily_min_: “Full-coverage foundation challenge… I had to try it too 👀✨” #fyp #beforeafter #skincare #glowskin #skincareroutine #kbeauty #transition #naming #layeredcover #foundation

Su🍎
Su🍎
Open In TikTok:
Region: KR
Tuesday 30 December 2025 00:21:30 GMT
62708
764
16
99

Music

Download

Comments

silvanahossain
silvanahossain :
Foundation name plz
2026-01-11 10:10:47
3
user2409123877043
Jo-Anne :
What’s the tape you used?
2026-01-09 13:06:50
2
lluna._69
ℓυηα🖤 :
Looks like skin🩷
2026-06-18 21:24:38
1
marya.shyrzad.sal
kcha-taqana :
name faundation plesss
2026-01-16 13:55:34
1
amy_not_founded
Amy🍩 :
🥰🥰🥰
2025-12-30 07:38:34
1
eleven4842
Eleven :
😳😳😳
2026-07-02 10:17:57
1
potatorrx
oopsiezz :
you lowk look Ai
2026-01-16 12:28:14
1
To see more videos from user @emily_min_, please go to the Tikwm homepage.

Other Videos

you’re not gonna like this answer... but there is no one-size-fits-all when it comes to picking a database. it really depends on what the app is trying to do and there are so many trade-offs. in my experience it comes down to sql vs nosql basically how powerful you need your queries to be and how much data you plan on reading and writing. if you have an enormous amount of data that you’re going to be crunching a lot, like in my subscription tracking app where i’m processing thousands of transactions, that’s a perfect case for a sql database because queries and reads are way cheaper. i would probably choose something like supabase, or if you’re a little more advanced, just use postgres directly on planetscale. if you’re vibe coding, supabase is great. if you’re just reading small amounts of data at a time or you need something streamed, look at firebase or convex. for mobile-first i personally recommend firebase because the sdk and libraries are just much more mature. it also has offline and caching out of the box with no extra work if you’re web-first, both are great but i lean toward convex. they have a lot of really good things out of the box for optimizing web apps. it doesn’t have things like offline mode but with llms it’s usually not too hard to build. the security feels more modern and the querying is much better than firebase. there are so many things that go into this choice and it’s always an oversimplification, so maybe i’ll do a full youtube video on it. this is coming from someone who has multiple projects on each of these platforms hope this helps! #softwaredeveloper #coding #appdesign
you’re not gonna like this answer... but there is no one-size-fits-all when it comes to picking a database. it really depends on what the app is trying to do and there are so many trade-offs. in my experience it comes down to sql vs nosql basically how powerful you need your queries to be and how much data you plan on reading and writing. if you have an enormous amount of data that you’re going to be crunching a lot, like in my subscription tracking app where i’m processing thousands of transactions, that’s a perfect case for a sql database because queries and reads are way cheaper. i would probably choose something like supabase, or if you’re a little more advanced, just use postgres directly on planetscale. if you’re vibe coding, supabase is great. if you’re just reading small amounts of data at a time or you need something streamed, look at firebase or convex. for mobile-first i personally recommend firebase because the sdk and libraries are just much more mature. it also has offline and caching out of the box with no extra work if you’re web-first, both are great but i lean toward convex. they have a lot of really good things out of the box for optimizing web apps. it doesn’t have things like offline mode but with llms it’s usually not too hard to build. the security feels more modern and the querying is much better than firebase. there are so many things that go into this choice and it’s always an oversimplification, so maybe i’ll do a full youtube video on it. this is coming from someone who has multiple projects on each of these platforms hope this helps! #softwaredeveloper #coding #appdesign

About