Dragging a page into the trashcan is inconsistent with deleting an element by hitting the trashcan button; it took me a bit of frustration to figure out. There's no way to figure out what the buttons do short of clicking on them to figure it out. Most features are intuitive but as evidenced by the "Actually it looks to me like it's only for iPhone design." comment the UI could use a little more explanation (there's no rule against using an icon /and/ text for menu options).
I really don't understand why there are so many negative comments, this is very nicely done and I can see it being useful. I'll definitely give using it a shot on my next mobile project.
Lots of templates, almost overwhelming. Looks great for detailed app interface prototyping.
I wonder about the code it exports - One of my goals with Edit Room is to have semantic, clean HTML and CSS that is as close to production-ready as needed, with skilled developers picking up the design prototypes, in close collaboration with designers using the app.
For more general communication designs, do check it out: http://www.edit-room.com (my project). It is perhaps more suited to the web design and publishing workflow. Edit Room takes up the task of complete visual design + prototyping. Inspired by AE and PS, but streamlined and focused on building high-fidelity, live, shareable prototype HTML/CSS documents. The visual design and animation editor generates flexible, responsive layouts that look exactly like what you've created on-screen. Etc... Oh, it works just fine with Firefox.
Cheers, and good luck with Fluid!
With the trashcan there are two ways to delete a widget - you can drag the widget to the trash just as with pages or you can use the button in the menu if you want less mouse movement for the action. We thought in that case that offering both methods is optimal.
Firefox that is.
I imagine if it was "Sorry, we only support IE9" you'd get a different reaction.
The reason that there's so much focus on web standards is because Microsoft used their browser to force platform lock-in.
I don't see going webkit only as being a problem: Chrome is available on the three major PC operating systems (Windows, MacOS, Linux), it's free and it's not owned by a PC OS vendor.
Now if it was Safari-only or IE-only, then that would be a problem.
So yeah, while you're technically correct by your wording alone, I'd argue you're wrong in spirit.
 http://www.webkit.org/ (see bottom left)
It really only sucks for general consumer-facing apps to not support a large variety of browsers. Otherwise, for specific apps with more tech-savvy users, just supporting a couple of modern browsers is just fine IMO.
While I don't think that webkit will stagnate the way ie did, it's really amusing to see the webdev community repeating the exact same arguments supporting webkit-only sites that we were about ie5-only sites 12 years ago.
I can understand the view that this would make you look worse, but my personal response is that I don't want to give your tool a second chance because of the annoyance (if everyone says it is the best thing since vim, of course, I'll get over myself and look :P).
If it was truly broken in Firefox I would've been curious enough to try it in Chrome. Sorry.
"We currently do not support Firefox but are working on it; for the moment proceed at your own risk, it may not work 100%".
Wasn't there an article recently about not treating early adopters like idiots. At least give us the benefit of the doubt.
Blocking outright just frustrates those of us who know better.
Right now, being blocked like this, I'm assuming by default
- You sniff the UserAgent (didn't test) instead of using feature detection
- You're basing a product on non-standard web technologies and will, like Google does, later provide 'Please UPGRADE to Google Chrome' (emphasis mine) links all over the site, as on this FF landing page.
Worse: There's no introduction to the site at all. So the topic says 'Mobile Mockups', but I don't even see an about page, some introduction stories, images or whatnot. I end up with a bullshit message that tells me to install a different browser for a product that I cannot check out without doing just that.
There's not much room to present a product less favorable.
Also, please add tooltips for various icons - they aren't all self-explanatory.
I'm using Opera, but I have a suspicion that it will work well with your app
Edit: Toned it down a bit, but I hate this kind of thing.
Just tells me no, you're not a fit for it.
For most developers who will use such a tool it's not a problem to install a webkit browser.
I myself have neither the grit nor the will to endure what you must have suffered, but I recognise this amazing achievement. As another poster has said, you deserve your $29 a month for your effort. I take my hat off to you sir.
Sadly, I'm not the person with the expertise to do it.
* for mobile designs
I was really looking forward to something like this, but incorporating elements from something like Twitter's Bootstrap.
You should check out http://delight.io
Maybe we can open up an API which your users can quickly get feedback on their prototypes.
It's just 2 people, I'm guessing the dev gets around $120/hr and the PM $30/hr? A Dev and Project Manager? Can you PM me their portfolio/website please?
Construct-O-Set : http://itunes.apple.com/za/app/construct-o-set/id373042556?m...
Wining and Dining SA : http://itunes.apple.com/za/app/wining-dining-south-africa/id...
22Tracks (Netherlands & Belgium only) : http://itunes.apple.com/nl/app/22tracks/id397202887?mt=8
ExpenZa (only available in South Africa at the moment): https://play.google.com/store/apps/details?id=coza.appositio...
22Tracks (Netherlands & Belgium only) : https://play.google.com/store/apps/details?id=com.fonkmobile...
Just as a note, if you want to log any issues/glitches or praise our support forum is http://getsatisfaction.com/fluidui - we are pretty active following up there.
We will try to reply to as many comments here as possible.
Here's a similar one for the iPhone library.
One thing this is lacking for me is a way to display page hierarchy or flow through the application. Just being able to connect pages with lines or arrows would be great. Or as a bonus it would be nice to be able to connect page elements to pages or elements on other pages.
* There is a problem moving labels in buttons/tables using the keyboard. Everything jumps
* The labels in editing and preview don't look the same
* Please add "Undo/Redo"
* Can't find a way to delete new window
I made two pages. They were overlapping (Not sure if this is intended).
When dragging elements onto the top page, they went to the bottom page. When I moved them around the top page they went to the bottom page.
How did you do it here?