Maker History
- ApyHub : The All in one API PlatformBuild, Test, Discover and Consume Powerful APIs
Forums
Descriptions for APIs - Looking for (developer's) opinions
Hi everyone, We are experimenting with ways to better describe the utility APIs that we building and publishing for our users. Please note that the audience is developers, so i am looking for their feedback. (I kind of like the 2nd option , just not sure how it comes across to developers) So here we are: Example: An API that generates a QR code About the API (1st option) The Generate QR Code API saves you the hassle of writing extra lines of code and allows you to create QR codes within seconds that can be easily integrated with your applications. The API can convert plain text or links into a QR code PNG file and customizes the output as a downloadable PNG as well as a URL pointing to the newly created PNG file that can be shared with your target audience. About the API (2nd option) Hello! I am Apyhub's Generate QR Code API. I exist to save you the hassle of writing extra lines of code to produce QR codes. Push me to generate dynamic QR codes for your applications within seconds. All I need is the text you wish to display or a link if you prefer to whatever you want your QR code to point to and I return a brand new personalized QR code as an output. What's more? You can choose how you want me to customize the outputs. I can produce PNGs and can also give you URLs. I am pretty easy to use, but feel free to read on to know more about the very few parameters I need to be customized to your requirements. Thanks!
We reached 4K users!
Hey PH community! It seems like yesterday when we launched on PH in November. And now, some months later, we have reached another major milestone. We ve hit 4K users!! *Three cheers* (thats 2x in the past 2 weeks) Exceeding our targets in terms of user growth feels great and gives me the right amount of energy required so we can focus on delighting developers A huge thank you to all our supporters and users- we hope to continue providing value to developers and engineering teams across the board. Please have a look at the linkedin announcement we made. :) https://www.linkedin.com/feed/up... cheers, Nikolas
First thoughts after yesterdays launch
Our goals: Someone could say that this is a straightforward answer: to be #1 product of the day or at least to be in the top 5. Right? Well, sort of. lesson #1 is: try to resist going for vanity targets, metrics and badges. Go for goals that are meaningful to your platform: Visits, registered users, community engagement. Lesson #2 : Having a hunter certainly helps especially if you are new on Product Hunt. We also debated over creating an upcoming page. Creating an upcoming page enables you to showcase your product and get some initial interest in the launch. Which brings me to mistake #1: Not creating an upcoming page as soon as possible. I won't lie: launch days at Product Hunt are quite fun. I enjoyed the outreach, seeing the comments pop up, seeing the visitors converting to users, seeing everything become alive. There is a certain adrenaline and excitement that is absolutely unique. Lesson #4 : Enjoy that day. Really. mistake #2: Relied on certain regions and mistake #3: Relied on new users. While we did a pretty good job in creating a buzz and engaging in discussions, we understood that many of the juicers we reached out to, had not actually made their product hunt profile. This approach penalizes the ranking - this is why we were #4 instead of #2. Overall, after our launch on product hunt, we observed: 1. High increase in site visits 2. 200x increase in registered users 3. Tremendous engagement and cool ideas around our roadmap Lesson 5#: Focus on growth targets, give the right urgency for signups (perhaps an exclusive promotional coupon for your plans) and engage in sincere discussions. We will keep doing this here: https://www.producthunt.com/post... More thoughts to follow, after we get some rest after the all-nighter. Best, Nikolas