Looks like a cheap Shopify site that one guy selling woodworking tools in Nebraska would have, not a startup with top tier venture capital funding. Hire some better designers
This is the second Launch HN in the last few days (the other being that macOS meeting widget one) that has left me absolutely baffled as to what YC saw/sees in it.
Sorry, I didn’t mean my comment to come off so negatively. I do wish the team the best of luck and think that reimagining aspects of the fashion industry is a very worthy ambition.
Haha thank you. For context, we launched on iOS, Android, and web within the same year, which has helped our marketplace grow, but we’ve since realized that we are outgrowing our engineering capacity (all done by me, a proud but headstrong full stack engineer ). Definitely maintaining a high sense of UX quality is one of our priorities, especially as we are trying to hire and dedicate better engineering resources to this challenge. Please let us know if you have specific feedback on the design!
hi kathy, congratulations on the site launch. there's one thing that stood out when I opened the site that you might want to take a look at. the 'onmouseout' behavior on the menu at the top seems like it needs to be reworked a little bit, because there is a tendency for the submenu to get 'stuck'. (its especially noticable if the mouse is in that position when the page loads). here's what i mean specifically: https://i.imgur.com/mbMnm4R.gif
second, i don't know if this is just my browser, but the images associated with step 1/2/3 (step 2 is missing) are vertically stretched kind of wrong, e.g. https://i.imgur.com/Hr63i0q.png
other than that, i strongly commend you for not using some kind of auto-hiding animation on the sticky header. and also not using animations in general. good call.
Thank you for the thoroughness! I appreciate any technical "eyeballs" on the site for finding bugs, and this context helps speed up the fixing process. Much appreciated!
Thank you! Haha I'm not entirely sure I recommend my approach. Obejctive C + IGListKit + regular old UIKit on iOS, React through next.js (for SEO) and native css on web, and Kotlin on Android. As to why: I've gotten a bit brash from my college hackathon years, as well as worked on a similar stack during my time as a full-stack eng at Pinterest. From sheer muscle memory and domain knowledge, building out Queenly on these three platforms was quick. Regarding mobile dev, on native dev vs. using React native, I'd say there's an advantage to being able to handle native navigation and animations, a wall that one might run into when developing on a hybrid app platform like RN. Additionally, a little company history: Queenly was an iOS-first app, launched first to prioritized our power sellers in our community. The React web app followed that, with enough user growth in between to shelve any considerations for a migration to RN.
I'll share but these are not necessarily strong recommendations haha—many of these decisions stemmed from what I used in the last few years as a full-stack eng at Pinterest, and being able to move quickly came from muscle memory from using these dev environments.
iOS - Objective C, UIKit, IGListKit
web - React on next.js and native css
Android - Kotlin
This is the second Launch HN in the last few days (the other being that macOS meeting widget one) that has left me absolutely baffled as to what YC saw/sees in it.