Preparing to post on Hacker NewsPieter Levels & Steve Ridout
As of my last training cut-off in September 2021, Pieter Levels is a well-known digital nomad and entrepreneur. He's the creator of Nomad List, a popular platform that provides data for remote workers and digital nomads about different cities around the world, including cost of living, internet speed, safety, and more. He's also known for his project, "12 startups in 12 months," where he launched a new web-based startup each month for a year.
Steve Ridout is less well known, but he's a software developer and entrepreneur as well. He's most known for his work on Readlang, a language learning application that assists with reading in foreign languages.
Please note that information about them after September 2021 is beyond my knowledge and you would need to check the most recent sources for updates.
First of all, congratulations on being ready to share your product on Hacker News. It's a great platform for getting feedback and potentially spreading the word about what you've built.
Based on the advice you've received and the examples you've studied, it seems that you're approaching this in a thoughtful and considered way. Your draft post is clear, informative, and it does indeed come across as real, friendly, and authentic. However, there are a few points that I would suggest you consider:
Title: It's succinct and does what it needs to do - explains what the product does in a single line. However, it might benefit from being a bit more intriguing or emotionally compelling. For instance, "Show HN: My AI language teacher helps you SPEAK a new language daily" might create more curiosity.
URL: Perfect, it's the product you want to showcase.
Text:
Product section: This is well-written, and the bullet points make it easy to understand the product's features. It would be great if you could provide an example of a conversation that someone might have with the AI teacher or a real-life use case that might help readers envision how they could use the product.
Startup section: You're honest about your journey and your struggles, which is great. People on Hacker News appreciate that level of frankness. However, you could consider reducing some of the personal commentary about your struggles and instead focus on specific problems you're facing that the Hacker News community might be able to help you with.
Sign off: You ask for feedback, which is great. It might also be helpful to prompt readers with specific questions. For instance, "What features would you find most useful?" or "How can I better market this without resorting to ads?".
About the decision of including the text field or not, this largely depends on the culture of the site and how you want to engage with it. Not including a text might lead to more people checking your site out of curiosity, but including a detailed, personal story as you have done could lead to a more engaged, thoughtful discussion and more valuable feedback. Given the nature of Hacker News and the fact that many posts that do well there include some kind of personal story or insight, your current approach seems appropriate.
Finally, be prepared for all kinds of feedback. Some will be positive and helpful, others less so. Don't be disheartened by criticism, but rather see it as a chance to learn and improve your product. Good luck!
Your revised draft is more focused and succinct, which is good. As for the specifics:
Including a Sample Conversation: I understand your concern about a sample conversation being dull, and you're right that the magic is in the personal interaction. But including one (even if short) can provide a practical demonstration of what your product does and how it could be used. It doesn't need to be long, just enough to help potential users understand what they can expect from using the product.
Getting Specific about Problems: You have identified that one of your challenges is marketing your product without resorting to ads. That's a clear problem statement that the Hacker News community might be able to provide insight on. Other specifics could relate to technical challenges, or decisions you're trying to make about which features to develop next.
Title: The revised title certainly grabs attention, but it might be perceived as negative or defeatist. You want to pique people's curiosity and interest, not make them think the product hasn't been successful. How about something like: "Show HN: A chatbot that lets you converse with a language teacher - looking for growth tips"?
Remember that the goal is to engage the community in a positive and constructive conversation about your product. Balancing honesty about your challenges with a positive outlook will likely engage more people. Good luck!
Absolutely, here are a few more title suggestions:
- "Show HN: A Language Teacher In Your Pocket - How Can I Improve It?"
- "Show HN: Speak and Learn with My AI Language Teacher Chatbot"
- "Show HN: My Chatbot Makes Language Learning a Conversation - Seeking Feedback"
- "Show HN: Redefining Language Learning Through AI Conversation - Suggestions Welcome"
- "Show HN: Want to Practice a Language? Speak with My Chatbot Language Teacher"
Remember, a compelling title on Hacker News should intrigue and accurately represent the content of your post. You might need to tweak these suggestions to fit your needs better, but I hope they provide a good starting point.
Your plan to share your work on Hacker News looks solid. Your text reads well, your title will catch interest, and you've included a direct invitation for community feedback. This is an excellent combination to spark a conversation.
However, I would like to remind you of a few additional things:
Timing: The timing of your post can have a significant impact on its visibility. You might want to research the best time to post on Hacker News for your target audience. There is no universally agreed-upon "best" time to post, but some suggest posting in the morning (PST) during the weekdays for maximum exposure.
Engagement: Once you've posted, be ready to engage with the community. Responding to questions or comments will keep the conversation going and show your commitment to and passion for your project.
Resilience: Hacker News is known for its brutally honest feedback. You might get some harsh or negative comments. Remember, the goal is to learn and improve your product, so try not to take anything personally.
Iterate: Use the feedback you receive to improve your product. If the initial post doesn't go as expected, don't be discouraged. Keep iterating on your product, and consider posting updates in the future when you've made significant changes or progress.
Best of luck with your Hacker News post and your project!
Yes, aiming for 8 AM Pacific Standard Time (PST) or Pacific Daylight Time (PDT) is often recommended for getting the most views on posts like this. Posting at this time gives people on the west coast of the United States (where many tech companies are based) the opportunity to see your post as they start their day. It also falls within working hours for the east coast of the United States.
However, keep in mind that the best time can vary depending on the day of the week and the audience you're targeting. Additionally, because so many people aim to post at these peak times, competition for visibility can be higher. Ultimately, while timing can help, the most crucial factor is the value and interest of the content you're sharing.
Your note ends on a polite and friendly tone, which is good, but if you're looking for something a bit more engaging, you could consider adding a line that encourages users to try the product and share their experiences. This way, you're not just asking for feedback, but also actively encouraging use of your product.
Here's how you could do it:
yaml---
Thanks for reading! I encourage you to give [Gliglish](https://gliglish.com/) a try, and share your experience here. Your insights and suggestions would mean a lot to me, and will directly contribute to the future of this project.
Looking forward to hearing from you!
🙏
Fabien
This way, you're wrapping up your post with a warm invitation for readers to engage with your product, which may translate into more traffic and feedback.
You're absolutely right. For Hacker News, a more concise and less directive approach might be appreciated. Here's a revised suggestion:
python---
Thanks for reading! If you've got thoughts or ideas, I'd love to hear them.
Cheers,
Fabien
This is much shorter and leaves it up to the reader to decide how they'd like to engage.
Here are some variations that use 'SPEAK' and avoid 'chatbot':
- "Show HN: My AI Language Teacher Encourages You to SPEAK"
- "Show HN: SPEAK to My AI Language Teacher for Practice"
- "Show HN: Practice SPEAKING With My AI Language Teacher"
- "Show HN: I Built an AI to Teach Languages Through SPEAKING"
- "Show HN: SPEAK and Learn With My AI Language Teacher"
Choose the one you feel best represents your product and would attract your target audience.
Certainly, both Pieter Levels and Steve Ridout managed to pique interest through simple yet intriguing headlines. Let's attempt to create similar intrigue while remaining descriptive:
- "Show HN: An AI Language Teacher You Can Actually SPEAK To"
- "Show HN: SPEAKING Practice With My AI Language Teacher"
- "Show HN: SPEAK, Don't Type, to Learn Languages With My AI"
- "Show HN: My AI Language Teacher Encourages Real SPEAKING"
- "Show HN: My AI Language Teacher - SPEAK to Learn"
Each of these titles emphasizes the unique aspect of your product, the focus on speaking as a learning tool, which is a distinctive feature not all language learning platforms offer. It stays within the pattern of successful posts by offering something intriguing and interactive.
These are excellent adaptations! You've managed to blend the successful format with your unique selling proposition. Here's how I'd rank them based on potential intrigue and informativeness:
- "Show HN: Gliglish – Learn a language by speaking with an AI language teacher"
- "Show HN: Gliglish – An AI language teacher to practice SPEAKING"
- "Show HN: I made a language teacher that uses AI to get you to SPEAK foreign languages"
The first one works well because it includes the name of your product (Gliglish) and a succinct, clear description of what it does and how it's unique. It will likely be more engaging because it focuses on the user's potential benefit (learning a language) and the unique method (speaking with an AI). The third one, while clear and descriptive, is a bit longer and might not immediately grab attention as well.
However, all three options are solid, and the choice depends on the message you wish to emphasize. Remember, no matter the title, the key to your success on Hacker News will be the innovative nature of your product, your openness to feedback, and your ability to engage with comments. Good luck!
Absolutely, I see how important these key terms are for the message you want to convey. Given your requirements, here are a few more suggestions:
- "Show HN: I built an AI language teacher that encourages you to SPEAK"
- "Show HN: Gliglish - An AI language teacher that gets you SPEAKING"
- "Show HN: I created an AI language teacher focused on SPEAKING"
- "Show HN: SPEAK to my AI language teacher: A tool I built for language learners"
- "Show HN: I built an AI language teacher to make you SPEAK"
Remember, a title is crucial for grabbing attention, but the substance of your post and product are equally important. I hope one of these suggestions fits what you're looking for. Good luck with your Hacker News submission!
Given your specific requirements, how about:
- "Show HN: I built an AI language teacher to help you SPEAK"
- "Show HN: I built an AI language teacher that gets you to SPEAK"
- "Show HN: I built an AI language teacher for you to practice SPEAKING"
Out of these, I think the second one is perhaps the most compelling and catchy. It suggests a direct action or outcome from using your product. Good luck with your post!
That's a great title. It concisely explains what your product does while also sparking curiosity about how it works. It includes all of your desired elements: "I built", "AI language teacher", "SPEAK", and "you", and it specifically highlights the function of your AI – to facilitate speaking in foreign languages.
It is clear, descriptive, and attention-grabbing. A potential user reading this title would understand that your product is an AI-based solution to help them actively speak and practice foreign languages. This is a strong title choice.
Your proposed title, "Show HN: I built an AI language teacher that gets you to SPEAK foreign languages," has a length of 78 characters, including spaces.
While it is true that shorter titles tend to perform better due to their quick readability, your title is still relatively concise and well within a reasonable length. Remember, clarity and accuracy should be your primary goals when composing a title. The purpose of a title is to inform potential readers about the content and encourage them to click on it.
Your title succinctly captures the essence of your project, which is more important than shaving off a few characters. It also effectively communicates the uniqueness and value of your product, which is essential for grabbing attention.
If you feel it's too long and want to trim it a bit, you could consider this alternative: "Show HN: I built an AI that teaches you to SPEAK foreign languages". However, this version omits the term "language teacher", which you seemed to prefer.
In sum, while the current title might seem a bit long, it doesn't exceed typical length limits, and its clarity and descriptiveness make it a strong choice.
Your post looks well-structured and compelling. It provides a clear overview of your product and its benefits, and it invites reader engagement with well-phrased questions. Here's a final proofread, with small changes for readability and clarity:
Show HN: I built an AI language teacher that gets you to SPEAK foreign languages
Hello Hacker News,
When learning foreign languages, I made the most progress by speaking them throughout the day, every day. This led me to create a site where you can speak to an AI language teacher to practice both listening and speaking.
The product
What I have now:
- Multilingual speech recognition: You can ask a question in English and get an answer in your target language.
- Feedback on your grammar.
- Suggestions: See examples of what you can say next to keep the conversation flowing.
- Speed: Choose a lower speed for beginners or a faster one for advanced levels.
- Translations: Click to see a translation into English (or another language).
- Role-playing: Practice real-life situations.
- Language Variety: The platform is available for learning American English, British English, Australian English, French, Spanish from Spain, Spanish from Mexico, Brazilian Portuguese, European Portuguese, Russian, and more.
What I'd like to add:
- More Situations/Characters/Customizations: A "Creator mode".
- Feedback on your pronunciation.
- Text-based responses: This would feel like a "create your own adventure" book!
- A dictionary.
- Phonetics: Zoom in and repeat a sound to help you hear phonemes and words more clearly.
- …and so much more!… ♾️ 😅
The startup
I've been working on this project for 6-7 months now.
While I love this project and have received many laudatory comments about it, I've found it challenging to reach a wider audience. 31% of users return to the site, and traffic is growing through word of mouth. Language teachers in schools and on platforms like Telegram and private intranets are sharing it with others, which is encouraging. However, praise alone doesn't pay the bills.
My goal is to achieve enough growth to cover costs, which would then allow me to focus 100% on the product (currently, I can only devote about 50% of my time).
A significant challenge is the widespread prohibition of self-promotion. I'm unsure how to navigate this issue and enable my product to truly take off. Paying for ads feels out of character for me, particularly as I use AdBlock everywhere. I admire Pieter Levels (@levelsio on Twitter) for his solo entrepreneurial efforts, and I aspire to achieve similar success. But it seems that something is missing.
What features would you find most useful? How can I better market this product without resorting to ads?
Thank you for reading! 🙏 If you have any thoughts or ideas, I would love to hear them.
Cheers, Fabien
Overall, your post is clear and engaging, and it communicates your passion and dedication. You've effectively invited feedback and conversation, which should encourage reader engagement. Good luck with your post and your project!
Your final selection "Show HN: I built an AI Language teacher to practice SPEAKING" is indeed succinct and highlights the key selling point of your product. However, for the sake of argument, there are a few points that could be discussed:
Lack of specificity: While it's true that your title is clear and straightforward, it doesn't specify what languages are being taught or how many languages your AI can teach. This may leave some people guessing or might lead to misconceptions about the product's capabilities.
Missing target user: The title doesn't specify who your product is for. Is it for beginners, intermediate learners, or advanced students? Knowing your target audience and making that clear could potentially drive more interested parties to your post.
Missing AI mention: The term "AI" is used, but it doesn't delve into how it benefits the user or why it sets your product apart from other language learning tools. The impact of AI on language learning could be a major selling point, especially for a tech-savvy audience like Hacker News.
Unclear benefit: The word "practice" might make it seem like your product is an auxiliary tool rather than a comprehensive solution for language learning. Using words like "learn" or "master" could provide a stronger sense of your product's capabilities.
Lack of intrigue: While clarity is important, some ambiguity can create intrigue and draw more people in. A title like "Show HN: I built an AI language teacher that gets you to SPEAK foreign languages" might pique curiosity and encourage more people to check out your post to understand how it works.
All that being said, your chosen title is still a strong option. It's clear, concise, and gets the main point across. The above points are just some considerations to mull over.
I understand your goal. After considering your target audience (Hacker News), the context (Show HN post), and the product (AI language teacher for speaking practice), I think the best title for balancing intrigue, specificity, and brevity would be:
"Show HN: I built an AI language teacher to get you SPEAKING"
The above title conveys several things:
- It's about something you've built (typical for Show HN posts).
- It involves AI (a topic of interest for the HN crowd).
- It's a language teacher (clearly indicates the field/area).
- The main feature or USP is to get users speaking (practical, functional benefit).
- It indicates an active process (get you speaking), which could create more intrigue than a more passive verb like "lets".
While your original option was great, this slight modification could possibly generate more interest and engagement.