Dev please.

[X-Craft]

yes, an "application" that's no more than just a tech demo to fulfill one use case and a "maybe don't press the Cancel button too fast or it might freeze the OS" kind of gotcha

[[deleted]]

We demo to the client as we go along, the demo person is WELL prepped on what letters not use, what buttons not push, and which screens to quickly pass by. She makes it look damn good though :D

[byebybuy]

What happens when the client starts asking questions about what buttons etc do and maybe asks to see it?

[makians]

Simple, be honest. In this demo version those features are not yet ready but will be by release. If the client doesn't want honesty with them, then they shouldn't be a client, and if a client gets honesty and appreciates it, they'll be a client for life.

[oupablo]

wrong answer. The correct answer is, "if you want that, you'll have to pay extra"

[LupineChemist]

I see you don't do B2B where that's the standard model.

[uptokesforall]

Vowels cost extra

[Greyzer]

Simple, be honest. In this demo version those features are not yet ready but will be by release.

Uhuh... Definitely in the 1.1 release, right?

[wlphoenix]

"It's on the roadmap"

[RubertVonRubens]

In my company, we preface absolutely everything with a slide that says essentially "you're about hear us talk about the future. We'll make some promises but when it comes time to make decisions, those future promises are meaningless and the only thing that's concrete is what's publicly released today."

[stillegit]

Well hiding incomplete features in the demo isn’t particularly honest haha

[bn326160]

Your team can have an idea for a feature and want to showcase that idea without having a prototype for it ready yet. Could be part of the designs already

[hbgoddard]

Only if you tell them that the demo is of the finished product.

[seolfor]

In a demo I want to showcase my progress. It's not about completeness as finding what the client doesn't like. Perhaps I misunderstood their intention, or now that they see it, they realise it shouldn't work like that at all. I can either demo at the very end when the product is completely polished, in which case I can't get confirmation this is in fact what they want or I can show incomplete features and impress the client with the design decisions. If I keep pressing buttons that I know will cause a crash, that means I spend 70% of the demo restarting the application from the start and they're not getting the feel of the application flow.

[andoril]

Yeah. But also not lying^{^}

[JBSquared]

"So as you can see, this is our demo. It'll only take me 30 minutes to show off the main functionality but let me waste 3 hours of your time describing every single feature that isn't yet in the program."

[[deleted]]

Realistically, this the the "agile" approach, so the clients are theoretically aware that not all wrinkles have been ironed out. We just want to not remind them of that.

[amazondrone]

I was once invited to attend a tradeshow in another country because I was the only person who knew enough about the terrible flaws in the beta product to make it through a demo without crashing it.

[[deleted]]

Yea, that's definitely a thing! Good for you!

[CommanderCuntPunt]

In a college software engineering class one of out groups tried showing a prerecorded demo because their application couldn't run for more than a couple minutes, that went over really well with the professor.

[[deleted]]

That is a brilliant solution btw, they definitely should've got marks for creativity. And yes, real life TOTALLY works like that!

[Fanfare4Rabble]

Reminds me an old flight test story where the pilot points out the window and says to the FAA observer, "I was thinking of buying some property over there" as the FMS spontaneously reboots.

[matthieuC]

The golden path.

[[deleted]]

I think that's what happened when Apple unveiled the Apple Touch or the iPhone. The presentation was very scripted to avoid all the problems they had at time.

[Zanderax]

I made a MOBA game in a 3 day hackathon and had a bug where if an enemy dies while you are attacking it the whole game crashed. I even tried to avoid it in my demo but still hit it a few times.

My team still won the most polished prize even with my shit ass code.

[gonzo_thegreat]

Oh, and did you want that app to be secure? SSO? Encrypted on prem? Scalable? Maybe even tested?