Stories

Lessons learned from launching my first product

Article news.ycombinator.com

Lessons learned from launching my first product

I created a tool named Logo Spark(https://logospark.starta.trade) for logo design inspiration and launched it on Hacker News a week ago.

As a programmer, this is my first independently developed product. I've learned a lot in the process, including understanding user needs, defining products, and marketing. Of course, I'm still a novice in these areas.

I'd like to share what I consider to be the most important lessons, as they will help me in future product development:

1. Using unfamiliar technology for the sake of coolness led to bugs: My product's core functionality has undergone extensive testing before and after launch, so there haven't been any major issues this week. The main problem was with the product landing page; in pursuit of a cool effect, I used a technology I wasn't very familiar with. Users immediately reported that the page scrolling behavior was strange and the experience was poor. I realized where the problem was and immediately removed the odd scrolling effect. In fact, I thought the cool effect would add points to my website, but it failed; using unfamiliar technology carries risks.

2. Users will object to my use of arrogant marketing terms: I claimed on my website that my product would be better than traditional logo design methods, but in reality, I had no data or evidence to prove this. Users also pointed out this issue. In fact, my product, like other traditional tools, is an auxiliary process in logo design.

3. The product requires login and payment to use, but lacks clear instructions, which annoys users: My product design requires login and payment to use, but there was no clear indication anywhere on the website, leading users to feel deceived. In response, I urgently added a notice at key points stating that login and payment are required to use the product and added 10 free usages as compensation for all registered users. New registrants receive 5 free usages to improve their experience.

4. Privacy policy and terms of service are controversial: Users expressed dissatisfaction with certain clauses in the privacy policy and terms of service, especially regarding the product's use of personal information and copyright issues with generated logos. I don't understand legal and compliance issues, and for now, I can only modify them based on other products' statements. I think this is something most products will encounter. I thought users wouldn't care about these terms (I never read them), but in fact, agreements are important, users do care, and developers need to balance the rights of users and the product well.

Thank you to all the friends who have given me feedback, and I hope my lessons can be helpful to everyone as well.

Discussion 0 comments · 1 points · hikerell · 2024-11-30
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    [ / ]
    Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.