What is Reddit's opinion of Moqups?

From 3.5 billion Reddit comments

I started in the front-end world so thinking about wireframe and designs is something that I got good at over the years. Wireframing is really just knowing a couple of tools that you are comfortable with. I used to start out making a wireframe in PPT and then adding design things unto it later with PS. Now I use a tool called moqups to create a pretty detailed wireframe. Then that wireframe gets transformed to html and then the design touch-ups can be done straight to the CSS.

If you have a client that you came into and they have a working product without a wireframe what I would try to do is try to sell them on making a wireframe of their project first, so any changes or enhancements would get through a round of wireframe approval before a line of code is written. This of course can be staggered accordingly if you have a team working. If the client has no wish to spend thousands of dollars to make a wireframe, I would at least try to make a wireframe for the parts of the application that need enhancements and try to do that way, still billing them for that time.

If it's a new project I don't start without a wireframe. I have been burnt too many times by people not knowing what they wanted. With the wireframe there are no arguments or unforeseen holes in their logic. Also once you have a whole wireframe it is easier to create data schemas and, just in general, framework your application in a much better way since you know exactly what you're building.

App developer here with some "Thank you for saving me hours of misunderstandings"

• Mockups and Flow Diagrams (http://yvonnelao.com/wp-content/uploads/2011/04/RW_FlowChart_121410.jpg)
• What does each button do? Does it change page? make a popup? perform an action?
• What features are CRITICAL, and what features are a bonus (sometimes you can't get everything done so you need to prioritize as a dev. Anyone who tells you they meet ALL their deadlines hasn't programmed large software)

Check up useful tools like - https://moqups.com/ or google "Mobile App Templates/Mockups/Visuals/Prototypes"

Best of luck!

<ADVERT> Feel free to contact me if you want to hire a cross-platform developer :) http://ca.linkedin.com/in/vjain8905 </ADVERT>

Mind map would be a helpful addition, I think this service combines a user flow nicely with UI: https://moqups.com/ But I'd still need to have the user stories/requirements as work packages that can be broken down into activities(tasks), then assigned, estimated, brought through workflows with different states, etc.

What I'd have to do currently is use a PM software tool separately like Jira, Trello, VSTS to assign and track tasks to devs. And then a prototyping/wireframing tool like InVision, Lucidchart, Google Slides to communicate with clients and designers. There is a lot of duplication of effort in having to use 2 segregated tools like that.

I do a little bit of web development. Have you ever heard of moqups.com?

it's what a lot of companies use when planning out a site. It looks like it would be complicated to use at first but mess around with it and you'll get the hang of it quickly. It allows you to draw out what you want your site to look like....and then you just go make it. Planning up front is huuuuuuuge when designing a site and implementing features.

Have you considered a mockup generator like https://moqups.com/ ?

If it were me and I had to proceed with this client I would establish a clear line of communication and eliminate the middle man in that , because for the most part that will slow down the turn around time.

But I would definitely not create too detailed of a mockup, and just concentrate on basic functionality, with basic layout, nothing too specific or details, because at this point in the project it's too early on to set things in stone. Thats where these mockup generators become handy, they help you concentrate more on the UI and not the design so much.

I found links in your comment that were not hyperlinked:

• moqups.com

I did the honors for you.

^delete ^| ^information ^| ^<3

I don't use Keep with Tablet. Mostly on Mobile. I use it to come up with very rough sketches while I am communiting in train.

&#x200B;

Yes, I do like Adobe XD (it's free).. I was using https://moqups.com/ for some time, but now moving onto XD.

Thanks for the input! One of the reasons that I was looking at Confluence was the Moqups extension that you can use with it (https://moqups.com/). It seems pretty great, but unfortunately, we couldn't properly evaluate it in the free trial period (7 days) so we didn't make the leap. Currently we're using OneNote which is working ok, but doesn't seem to have any tools to help us out that I've found.

You're right though, getting organized around the content is pretty key!

https://moqups.com/

It's been a while since I used it, but I found it really useful for communicating design ideas with less tech savvy people in a different state. I think the free version lets you have two saved designs.

Oh i think as OP , something got lost in my description and ( after re-reading I see what it was )

I am the dev and I can build from the design kit and make mockups. ( Brackets is cool but stay far away from Dreamweaver , haven't tried a new version so maybe i'm bias )

But the problem is analyst on the team are not dev savy and often use photoshop or cut and paste in a word document their concepts for a page layout.

Is there a way I could bridge the layout into a wysiwyg editor. Sort of a build your own UI like fluidi or moqups . but with the ability to inject your own code directly so all that can be used is your own inHouse design kit.

working on user experience is is huge for us. I know that is not a "tool" but driving out interactions that make our customers happy and save them time is a huge deal for us. we are a B2B SaaS and the software that our clients use is extremely out dated and they have huge long cumbersome processes for everything.

a tool I like to quickly iterate through ideas is moqups https://moqups.com/

Acctually before my game I made just one app that is in store and I got everything I needed (mockups etc.). I didn't do this for my game.

I played a bit with Moqups but nothing big.

My main issues with the app are similar to others stated. The graffiti clean contract hasn't been up for a bid in years. The same LA based company has had the city contract, and their one selling point was an app that they outsourced!

I don't know about an app costing millions, but hopefully my app will be self sustaining through locally owned business advertising.

Here's our original moqup if anyone would like to offer some input. https://moqups.com/conexionbayarea/wLO1kMBP

www.sanjosedistrict5.com

Sorry I was wrong... I just looked at the library and it should work with my code. You will just have to work on the GUI which can be done with trial and error by adjusting the pixels or by using an online site like https://moqups.com/ to work it out for you.

I start with pen&paper. I'll upgrade to https://moqups.com/ once I've decided on a general idea/feel.

If you're writing HTML/CSS, you aren't wireframing anymore. You're implementing. It's slow. For me, writing code doesn't come into play until I'm fleshing out a prototype of a wireframe or two that we've decided on.

> Also, I just want to say that one response I've seen a lot in looking into this is that wireframing should be started with pen and paper. While I agree, and I have done this, I need something I can easily send over the internet and also hope to make it look a little more professional than my drawing skills allow.

Check out https://moqups.com/.

The tough part about being a frontend developer is that you aren't necessarily a designer, just a programmer. A lot of frontend devs do both though, but not all.

If you are able to, then you could design + build, which would add both design and dev work to your portfolio. Otherwise, you could look at websites on the net, use them as inspiration, and create something pretty similar to those sites. You could even develop wireframes too if you so wish to do so (and add those to your portfolio as well). Here are some tools for mockups: http://mashable.com/2010/07/15/wireframing-tools/ https://moqups.com/

Finding local businesses is cool, but time consuming (and those businesses probably already want portfolios). Starting out can be tough :)

Really curious to see how this turned out!

The comments above are solid, but I thought you were more asking about how to engage as a first time freelancer? If so, I would recommend you consider this first client as the start of your new freelancing business and as redditbotboy says, think about the process of engaging: business needs discovery, prototype, proposal, engage, develop, demo & iterate.

I think, especially for a first time freelancer, you should spend a lot of time in the first stage of business needs discovery and prototyping. I highly recommend using the Moqups service to develop your proposal collaboratively with this client: https://moqups.com/home/