I recently evaluated mockup apps (from Balsamiq to Moqups to Mockingbird to Axure) for a new project of ours, and nothing I found gave me what I needed—which was the ability to mock up interactivity in a predictable, easy, and non-tedious way.<p>I made my own library instead to simply control state in an HTML page using simple, logical class names and IDs. This, combined with Bootstrap, made an HTML mockup a very fast and easy way to do exactly what we needed.<p>Is there some new feature in Moqups that helps with interactive state such as this? Or do you have any suggestions on what the "best practice" for interactive UI mockups should be?<p>Or is this something people don't usually do? Is it seen as "too realistic" or unuseful? So far we've found the interactive mockup invaluable in honing generic UIs and determining which direction to go, so I can't believe it's so difficult in most tools to control and easily switch component states.
This is a totally trivial nitpick, but when I see 500MB at the $9 level I start to do multiplication in my head and kind of get distracted. If it wouldn't cost you too much more, I would suggest considering 1GB for that level. The little story told by the levels just seems simpler that way to me. Like I said, totally minor point, and perhaps it's just me so take with a lot of salt.<p>Congratulations getting to this stage! The price levels seem reasonable to me. I personally wouldn't have a problem paying for it.<p>Is there integration with Basecamp or similar? That would be nice.
Hmm, this is a really great product and I've loved using it, but 2 projects? That's so ridiculously low that 'free forever' seems a bit hollow and vacuous now. It would be better if you just came out and said it. Are you just supposed to go one humungo project now?<p>I'm certainly not paying a monthly recurring fee for a mock up tool to play with side projects! I could see upgrading it for the collaboration aspect for clients, but for toy and hobby projects you've seemingly just killed the tool.<p>Calling it 'using in a casual manner' is bad, how is having a project per idea and being limited to 2 ideas 'casual'? A helpful compromise?!?<p>Personally I think you've focused on <i>completely</i> the wrong thing to go premium for. I'm surprised you didn't go private projects & apps/dropbox integration (standard) > revision control & master pages (pro) > collaboration (ultimate) or something like that. But that's just the programmer in me I guess, we all know that multiple projects won't add to your costs, just massive inconvenience to the free users.<p>Still, it's your product so do what you want and you're allowed to change your mind, just don't expect a lot of people cheering you on. I'm just personally sad I probably won't use it any more as I'm not going to faff around trying to organise multiple thoughts into one humongous project.<p>As a reminder of what you originally said when you introduced it to HN:<p><i>We'll keep the main functionality free (with some reasonable limitations). We plan on adding some really cool collaboration and annotation/feedback features soon that we'll probably ask a buck or two for.</i><p>I just don't see 2 projects as reasonable at all but I always suspected something like this would happen as the tool was just too well done. Note that I would probably buy it for a reasonable fixed price (like $50-70) but obviously the storage, etc. will constantly be a drain on you. It is better than balsamiq, but not better enough to be dipping into my pocket every month for the rest of my life. The problem with saas I guess.<p>EDIT: I guess this is the problem with an online tool being useful to both individuals and corporations. I can see real value from a recurring fee from dropbox as an individual, but a mock up tool? For what (should) be a desktop app that's gone to a sass model, are individuals really going to pay a recurring fee for this? On the other hand, it's a perfectly reasonable price for businesses, even small and micro ones if you use it regularly. I would definitely sign up if I do more consultancy again. Perhaps I'm cheap as an individual, but to me it's just far too expensive for my personal use case.
Finally! These guys rock.<p>I prototyped our startup's entire user flow with Moqups and I couldn't be happier ... their way of configuring elements from a plain textfield with a Markdown-inspired philosophy works really well for me.<p>I literally asked them when I would finally be able to pay them for privacy controls a while ago ... they haven't mailed me yet though ;)
Seeing a paid option always makes me a little more comfortable using a product. It gives your product a sense of longevity. Congrats on launching premium!<p>Just a simple gripe on blog design. A few months ago someone posted an article about an all-to-common problem [1] in company blogs. Your site doesn't have any link to your actual product. Luckily this article has a link, but unless every article links to the product, you are losing business every time. You're forcing your readers to manually type in the URL instead of having a simple link in the header of every page. It's a simple fix, but it could pay off big time.<p>[1] <a href="https://news.ycombinator.com/item?id=5267330" rel="nofollow">https://news.ycombinator.com/item?id=5267330</a>