It's an interesting read but I hope the OP takes away more than a renewed drive "to show them".
For an outsider it looks like a classical "overengineering" kind of project. You say it's too complex a problem to test early but if you reapply keep this in mind "validate you're not heading down the wrong path as early as possible" is the mantra. You seem outraged that XCode was suggested for example but you should have had a very clear non-technical response. Maybe list stuff like Ionic or even rapid prototyping stuff like Quartz Composer with Origami. Then link them by saying you can essentially build apps as if using Origami but get close to native performance, better code etc (mind you the JS to native compilers and pure JS folks will make similar claims)
Who's your target audience. Programmers becuse it takes them less time, designers because they can get further without programming?
I think you (the devs) should sit down for a coffee and talk through your project without going technical. Think of it as hacking the application process if you want. Fill out a Lean Canvas for your product even if it seems silly. Grill each other as if reliving the interview.
tl;dr: Pretend you're talking to nontechnical people and ignore everything that feels like "did they even read our application". Just mentally imagine they have invited you because someone recognized this as a hard engineering problem and now they are mostly interested in the business side.
For an outsider it looks like a classical "overengineering" kind of project. You say it's too complex a problem to test early but if you reapply keep this in mind "validate you're not heading down the wrong path as early as possible" is the mantra. You seem outraged that XCode was suggested for example but you should have had a very clear non-technical response. Maybe list stuff like Ionic or even rapid prototyping stuff like Quartz Composer with Origami. Then link them by saying you can essentially build apps as if using Origami but get close to native performance, better code etc (mind you the JS to native compilers and pure JS folks will make similar claims)
Who's your target audience. Programmers becuse it takes them less time, designers because they can get further without programming?
I think you (the devs) should sit down for a coffee and talk through your project without going technical. Think of it as hacking the application process if you want. Fill out a Lean Canvas for your product even if it seems silly. Grill each other as if reliving the interview.
tl;dr: Pretend you're talking to nontechnical people and ignore everything that feels like "did they even read our application". Just mentally imagine they have invited you because someone recognized this as a hard engineering problem and now they are mostly interested in the business side.