Took me a moment to notice the "shuffle" button; the utility of the site became a lot clearer after that!
Are those real peoples' photos? I know this is intended for mockups and placeholders, but the absence of any licensing info would still give me a little pause before trying this for anything but a personal project. (I recognize the 'fake logos' from logoipsum.com, they don't require attribution but you miiiiight be on the wrong side of the line of their "as long as you don't use the logo to make similar website as Logoipsum then it's all good" thing.)
I hate to be the copyright party pooper, but this is a nifty idea; a quick note at the bottom confirming sourcing and that everything's openly usable would probably encourage more people to make use of it!
Certainly not the portrait photos — they’re unmistakably sourced from https://thispersondoesnotexist.com/ (once you’ve seen enough of them, they’re impossible to miss…)
That's a good point -- our goal is for everything on the site to be able to be used without any sort of attribution. I think it's that way now, but will go and double check everything we're using today
Hey HN, Alex and Ben here, and we wanted to share a simple web app we created recently.
UI Filler is a quick way to get placeholders for your designs.
We do a lot of UI design and development and frequently need to fill it with placeholder content. I usually just Google “Lorem ipsum” and end up on a site about the history of lorem ipsum, then copy and paste some small chunk of it to fill the field I need. Ben, who is even more design-oriented than I am, tries to make up appropriate text to fill fields (my favorite thing he does is placeholder names, like “Anita McLaren”). We decided to make a tool that would save us a bit of time every time we needed a placeholder, so we built UIFiller.
I'm about to build something similar, not as a standalone product, but as an internal component for a side project of mine. If this could be fleshed out, and delivered as an API, I'd pay for it.
Great idea, thanks for this! The only thing I would change is the background color of the site. The high visibility jacket green does not contrast well with the white boxes and dark gray text. I also get a bit of afterimage, but that's probably because of me.
Yes! A JSON RESTful API GET endpoint would be SWEET! Easy scriptable way to populate a local testing / design resources folder with some fast starter data. Just to name one possible use that came instantly to mind for my uses. Love the random seed idea, too.
Nice idea, I could imagine using this. Just a thought, it might be nice to see more variation in the Lorem Ipsum, like with text that include numbers and links and capitalized word, maybe even multiple paragraphs.
This makes a ton of sense as a browser extension, why not go that route? With this, I still have to google your site (or at least type it into the url bar if i remember the exact url)
If you use it a lot, this makes a ton of sense as a bookmark on your browser's quick access bookmark bar, sidebar, or new tab page. It would also make great sense as a script accessible JSON API endpoint, as another reader here suggested.
If you aren't testing your interface with names like Ferdinand Zvonimir Maria Balthus Keith Michael Otto Antal Bahnam Leonhard von Habsburg-Lothringen, you're doing it wrong.
This is almost perfect, just need a few more special characters. Fortunately, Ešeeva'e Ó Cuinneagáin Sólveig doesn't mind being a _very_ early adopter.
Edit: I bet this post looks pretty stupid now after parent edited to include special characters.
> after parent edited to include special characters
I added the city, because I remembered about it. Frankly, I didn't know that Polish had that many diacritics, specifically considering their unfortunate crash into all the digraphs. Ferdinand's name is left as it was, and your point is valid and valuable.
BTW, I had no success googling the name you provided. Thought it would be someone vaguely famous.
Once this becomes the next decacorn, we're going to get Ferdinand Z. M. B. K. M. O. A. B. L. von Habsburg-Lothringen to be our spokesman. Heck, Ferdinand -- if you're in the comments, you can be our spokesman now if you want
To provide relevant data for a acceptance (manual) testing environment. Avoid using production data there.
To create (temp) mock web APIs in a database, so frontend and clients can start development while the backend builds the actual business logic.
To fill a database in development with which a dev can build the UI and views. This uses the same data files and pipeline as the first.
For this, I basically just download and transform one or more CSVs and or JSON files. And commit them as part of the software. The official import pipeline of a backend can ingest those in e.g. a CI or with local scripts.
Basically just a ./fixtures/members.csv, jobs.csv, vacancies.csv etc.
One of these days I’m going to build something like this, but with realistic profile pictures. A UI with pictures like this site has will always look great, but now try it when half the profile pics are the user’s dog, or the user standing in front of the Eiffel Tower, or hanging out with fifteen friends in a bar. Suddenly it goes from “oh, that’s a post from Bob” to “what even is that picture”?
Are those real peoples' photos? I know this is intended for mockups and placeholders, but the absence of any licensing info would still give me a little pause before trying this for anything but a personal project. (I recognize the 'fake logos' from logoipsum.com, they don't require attribution but you miiiiight be on the wrong side of the line of their "as long as you don't use the logo to make similar website as Logoipsum then it's all good" thing.)
I hate to be the copyright party pooper, but this is a nifty idea; a quick note at the bottom confirming sourcing and that everything's openly usable would probably encourage more people to make use of it!