Hacker News new | past | comments | ask | show | jobs | submit login

You also need to account for losing internet connectivity. I had a demo before I knew what I was doing where I went to the customer site and they set us up in some sort of dead zone, essentially could not connect to either guest wifi or mobile hotspot to show the product for most of the time or when it did connect the lag was so bad it seemed like the product was incredibly slow.

Most places will not allow you to connect via a wired connection to their network for good reason.

I then started tripping all over myself because I had not prepared for this situation. I did not land the customer.

If possible, running on local host is the way to go.

It was a character building experience.




...and when running from localhost, watch out for any resources loading from a CDN, and, of course, for your local dummy data being total crap and/or accidentally offensive (and get ready for "Why is all this text in [Latin/French/Italian/something really bizarre]?" when you use lorem ipsum).


I learned long ago that -any- placeholders confuse people. Image placeholders? "Why is it showing me just an image of some random person with the word 'placeholder' over it?! I would have images of Y!" It's frustrating, but that's reality. Figure out the sort of thing users will actually have in there, and try to put something similar. Preface lorem ipsum with "Your text goes here. Fake text follows: Lorem ipsum dolor sit amet..." or similar.


A million times yes. I had a client tell me an example draft deliverable was "the worst document I've ever been handed" when I was showing them a preview of the document format in week two of a three month project. It was supposed to be documenting their entire architecture and solution I was building for them, so it would be delivered at the end of the project. They asked to see it early, so I put in placeholder data. They were not impressed, and it nearly tanked the whole project. They didn't want to pay thousands of dollars for obviously placeholder text. Problem is, none of their real information had been fleshed out yet, so I didn't have real data to put in.

But then on another client, I put in better (more realistic) placeholder text for the same document and they thought I had sent them another client's information and got real scared about their own data privacy with our company. That's when I learned to refuse a client's request to show them a document before it's (at least nearly) finished. If they want to see the format, a static picture of very obvious placeholder data serves just fine.


Good idea! If it's an image, you can watermark "DEMO" or "DRAFT" very visibly over it, and that hopefully will help them realize it's neither real, nor intended to be what is submitted.


I think a large part of the problem comes down to two somewhat related things: people only understand things based on their own experience, and people have very little imagination.

As developers, we spend all day building things that don't have the right or final (or any) content, and we understand that a box filled with lorem ipsum will look fine once the real text (which doesn't exist yet) is in there, or a screen with just a big red rectangle adorned with "PLACEHOLDER 500x300" will look perfect once the final image is inserted. But for consumers of what we build, they have no experience of non-finished products: they don't ever see placeholder images on Facebook, they don't see unwritten copy in the newspaper, and when they open up Microsoft Word, they don't type "The quick brown fox..." into it, they type the actual text they want. We know that the hard work from a development perspective has been done, and it's now someone's job to write the copy and pick the images (which is, of course, no easy job)... but to the end user who has no concept of the code whatsoever, all they see is a page where everything is totally wrong.

Secondly, imagination: if all they can see is a red rectangle, many people will find it very hard to imagine a tastefully chosen hero image there instead. We built a product a while back which, in large part, was intended to be flexible and extremely configurable - that was a really key feature of the software. When I was initially demoing it, I showed it in two configurations: one that was incredibly basic, and one that was a wild mix of various garish colours and fonts. I had anticipated that people would use their imagination to interpolate various tasteful designs between the basic and the garish, but no - all they could see was boring or ugly. Even with a careful explanation - "Of course I've used awful colours, you can easily choose from your corporate palette!" - it just never went down well. (Now when I demo it I show off the configurability by tweaking in real-time two pre-existing designs, very different but both very pretty, and both of which are firmly grounded in real-world use-cases, which avoids nitpicking like, "Well, it looks very nice, but we'd never use it like that, we'd have another foo after the bar...")

To the guy saying to use Bacon Ipsum, just no. That's fine and funny when you're a developer sharing something within a development team, but otherwise for a surprisingly large number of clients it will be confusing and possibly seem extremely unprofessional.


For Python, I've used the Faker package to generate dummy data. It was quite easy to use, and much better than the homegrown approaches I'd taken in previous projects.

http://faker.readthedocs.io/en/master/index.html


Thus you consider options like Bacon Ipsum or Simpson Ipsum (among others on http://www.designsmix.com/web-design/15-lorem-ipsum-alternat... )


The solution -- I ran some demos in a previous life -- is extensive screenshots, plus static html to move between them. Everything should be totally canned. This shouldn't be your demo, but it's the backup for when internet connections go to shit and you don't want to be just screwed. This will also help when god realizes she hates you and your app breaks just before a demo.


This could be a pretty cruel way to vet somebody. Intentionally deny them wifi access and see how they react. Perhaps more competent companies perform better? More likely people just flop.


This may seem old school but I actually have a printed out spiral bound deck customized to the client that I take to pitches. In addition to the digital presentation.

I do it for a few reasons:

1. Because our service is expensive and some more old school clients want to hold something in their hand

2. It sits on their desk pretty much forever, keeping the brand in front at all times

But it has the added benefit that even if the power goes out, I would still be able to pitch.


I had a boss who did this to haze vendors whom we had to meet with but had no interest in.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: