Live data from Hacker News

Ask HN: please review my site - Marrily.com

news.ycombinator.com

1–10 of 73 posts

Ask HN: please review my site - Marrily.com

#1
Hello everyone,

Please help me review my site at http://marrily.com

Please use the code "hackernews" when you sign up (this is still a close alpha release so I put in a code to help me track the signup users)

If you are planning your wedding, or just got married recently, please sign up and test Marrily out. I'd love to hear your opinions.

I'm the single founder for Marrily, and today is the result of an intense 3 months of me bootstrapping and developing the app in a cave then finally come out to see the sunlight, and shouting from the top of my lungs that Yes, Marrily is out!

Marrily is a word I came up with, it means to "Marry Happily." I wanted to help people getting married easier and less stressed, and the existing sites aren't all that great (I'll write more about this later in Marrily's blog.) Even though the real development took 3 months, it actually has been 3 years since when I came up with the idea and actually built and release the app. If I'm to learn something from releasing Marrily, it's probably perseverance and grit.

I decide that when I launch Marrily officially, it will be a premium app (e.g. pay-to-play, as apposed to freemium). The reason why is I believe that if I build a solid app that is useful and easy to use, and can potentially save people a lot of time and efforts, then it's fair to charge a small fee. With the freemium model, it's harder to code (limiting features in code can make things a lot more complicated) and can affect negatively the revenue (if the free one is so good that it doesn't make sense to upgrade). But I welcome your ideas and suggestions.

However, there's no subscription mechanism in the alpha release (I stil have not implemented any of the subscription handling code yet!). I estimate that it will take a few more weeks to finalize the app and have everything in place for the official launch.

Since you're one of the first people to see the app in its entirety, I'd love to have your feedback as you use it. More specifically, I'd like to know if you run into any issue navigating the application, and if something does not make sense to you, I'd love to know. I have tested as much as possible to make sure it is stable and ready for production use. But being a single founder, it's sometimes a challenge to keep track of every changes in the application.

It's been an amazing journey, and a life-changing experience, so I'd like to share this moment with all of you, and many thanks to the HackerNews community for being so awesome. I learned a lot about myself and entrepreneurship in the past few months, and I promise that I'll give back to the community to help more entrepreneurs fulfill their dreams.

Alex alexle@marrily.com

Re: Ask HN: please review my site - Marrily.com

#7
Too much text. I know you want to get your app out and screenshots are in the works, but it still must be said:

  show don't tell.
Features are all text, need visuals.

When I sign up and enter the admin I am lost. Takes me a while to figure out what to do. A guided quickstart guide would be helpful. Navigation menus that are directed either by arrows or numbers also help. I suppose if I already paid then I will take the time to fill in all that stuff. But since I didn't pay it's very hard for me to care about filling in information. Therefore you have to make it as intuitive, easy, and guided as possible. Reward the user visually.

Best advice is to seek out brides/grooms sit them down and watch them use your app. Do this over and over. Chances are your app will be very different than what it is now.

I like the feel and the domain name is good. Congrats on launching, good luck!

Re: Ask HN: please review my site - Marrily.com

#10
Upon registration, the page (create event i believe) is too wordy. At first, I did not realize that I had to select the date of the wedding to move forward to anything. I clicked on the links up top but all of them kept reloading the page (the css seemed broken for an instance or 2). IMO, clearer and much shorter, to-the-point instructions are necessary. A small walk-through or a quickstart guide directing the users as they start using the site would work well for you.
Post reply on HN