Hello, Product Hunt community! I built something cool last weekend. In between working on my startup and raising four kids, I wanted to get back to coding So I built the Cerbos Game a brain-teasing challenge where players match incoming requests to permission policies: just like what Cerbos does for software applications. Think you can make accurate permission decisions based on predefined rules? Give it a try: https://game.cerbos.dev/
This game disrupted our engineering team s daily work while they were trying to beat the high score. Warning: it is really addictive If you re up for the challenge, drop your score in the comments! Beat the top score, and we ll send you a full pack of Cerbos swag. But fair warning our engineering team has set the bar high.
And if you're wondering why I built it it's a fun way to showcase how our product works and makes secure authorization decisions. Also, I really enjoy my hacking weekend.
Hey everyone! Aaron from the community team at Product Hunt and one of my newest big interests is building with no-code, I'm always on the lookout for cool ideas built with no-code for discovery and also for inspiration, I'd love to get a thread going of all your favorites here, lets inspire each other!
Happy to answer anything related to Product Hunt, social media, student makers, me(?) I'd also really appreciate it if you have any suggestions about what you'd like to see us do on social
Hi makers! Many of you are launching products, or getting ready to. I'd love to know what the hardest things about launching are, or hear what your concerns are. I'm here to answer any questions and share some honest advice. I've been on the community team since 2017 and have seen over 1,000 launches since then!
A bit about my experience: Apart from a few pivots, I have worked with food for around 7 years, I have left the food industry to work at Product Hunt but it still has a massive place in my heart. Within my experience, I trained as a cook (Italian), a bread baker and during my Italian training I also was a pizzaiolo Currently I'm teaching myself Indian cuisine, which is probably the most exciting thing for me right now. I also cook at the Product Hunt off sites for the team Ask me anything you want about cooking, the industry, technique, the culture within a kitchen, anything really!
The Golden Kitty Awards are now open for voting! It's your chance to make sure a trophy ends up in your fave makers' hands. So have you voted yet? Pick your winners here.
I'll have to go with @csallen Reason: Ships code, Creates Content and Builds community. The real Founder Unicorn. Who's your top pick? PS: Be fun and don't nominate yourself :)
Yesterday I read a lengthy discussion on YC HackerHews that no-code is just "a buzzword". So here are my two cents 1) No Code is BIG.
Gartner estimates that "by 2024, low-code application development will be responsible for more than 65% of application development activity". So no-code is something we should take very seriously because as a trend and as an industry it will only grow. The capabilities for product development are huge, while no code & low code tools will only improve in functions. For example, I founder a no-code startup, called WeLoveNoCode (https://welovenocode.com/) which helps startup founders hire no-code developers and build products 10x faster. We got $1M funding, grow to $150K MRR, and made 2000+ projects. It's not a joke, this market is huge! 2) No code is USEFUL
No-code is the art of creating solutions (native apps, websites, web apps), which could have been written with code but instead using visual methods (without coding). Most no-code tools use a visual drag-and-drop interface. In addition, a lot of them have pre-built templates that you can customize. There is also a slight difference between "low-code" and "no-code." With "low-code," you can do many things with a drag-and-drop interface; however, some coding is required for a finished product. So you ANYWAY need some background in coding. Low-code is typically great for people with intermediate technical skills. No code is a new way of building products, very different products. It's not magic. What can be built with no-code? * Mobile apps, * web apps, * websites, * workflow
* automation, * marketing tools, * payment systems and the list goes on. Basically, "typical" products & MVPs benefit the most from no code. So the founder can build something in weeks, really fast. For example, WeLoveNoCode connects founders with the best no-code developers to create their software and apps without a single line of code in like ten days. You can do all of these on a monthly subscription plan. 2.) No code has proven its place already and it has A LOT of the advantages: * will save you money
* you can build and test your ideas quickly
* anyone can use it > Designers, product managers, marketing managers now can make their ideas tangible products. Just like a new thing, tools have to be learned, and they all have their learning curves. However, it will take you much less time and resources to learn how to use no-code tools. Unlike low-code tools, no-code tools have a limit to how much you can customize them. So if you want to change every aspect of your product or build very complex products, no-code tools may bring some limitations. However, there's so much innovation and growth with these tools, so I expect fewer barriers in a few months.
I'm on 20 days visit streak. Use this discussion to flaunt your streak numbers and share your last week's favourite product. I'll go first Better Viewer by @adem_kouki https://www.producthunt.com/post...
I picked "Maker Mindset" topic on purpose :) I carefully review most of the products that I like and comment on here for vulnerabilities or security flaws and the result is not good. Yesterday I discovered a big problem in one of the products for example allowing attackers to exploit it. (I have notified the makers of course) So my question is - as a maker - do you think about security at all when you design and implement your idea? Is this one of your checkpoint items as good UX, nice design, value, etc?
Hey Makers Aaron from Stark here. A lot of us will likely be bfuilding and launching products throughout the year so it s a good time to strategize on how we approach accessibility efforts. I wanted to ask where in your product lifecycle you start thinking about accessibility?
Result-driven is not a number of launches per quarter, the number of written articles, amount of paid sponsorships, or people who attended your community event. Neither is it the number of followers you have on your social or the weeks you spend on your user research. It's basically two things: leads and revenue generated. Every marketing function will have key results that will lead to those outcomes. So how do you make your team "result-driven"?
I ran a similar experiment on Twitter a while ago and realized I should have asked the Product Hunt community. First, some context: I started Weekend Fund in 2017 while I was still the CEO at Product Hunt. Today, @vedika_jain and I write $100K to $300K checks into early-stage startups (most of which launched on Product Hunt at some point). Our background is in product and community building, but we have a network of over 400 LPs across every domain from data science to enterprise sales. More details at weekend.fund. If you're primary KPI (revenue, MAU, etc.) is growing 20%+ for 6+ months, drop me a note with details ryan@weekend.fund. If you have a deck, please share but we'd also love to chat with founders that aren't actively raising but could use our capital and help. :)
