4 ms·
It is based on "Show, don't tell" but it is not that easy to do. I think the Twilio presentation was impressive because automating SMS and getting a phone numbe
by wslh 10y ago
It is based on "Show, don't tell" but it is not that easy to do. I think the Twilio presentation was impressive because automating SMS and getting a phone number was difficult and required slow back-end setup. It was a simple concept to understand but difficult to implement. Stripe example also simplify the work with payments.
The problem is: how do you follow these principles for less obvious applications? For example, how do you impress your audience if you sell a database engine? It is a good startup exercise to think about it. I would be impressed with a tool to quickly design a web application in the same way Visual Basic did 25 years ago instead of talking about Bootstrap, Foundation, AngularJS, React, etc.
- atonse 10y agoRegarding impressing the audience with a database engine, I think it was rethink who did the demo of a cluster of a dozen Mac minis and they'd start unplugging them and whatever steam of data never ceased. I found that quite impressive. Was it Rethink or MemSQL or some such? Anyone else remember that video?
- deleted 10y ago[deleted]
- meredydd 10y ago> I would be impressed with a tool to quickly design a web application in the same way Visual Basic did 25 years ago Me too! So we built one - https://anvil.works https://anvil.works The "Hello World" app takes 45 seconds (there's a video on the homepage). The "Display a slideshow of images from Google Drive" app takes a whole five minutes, because I talk through it slowly (video at https://anvil.works/learn https://anvil.works/learn - scroll down). If you want to demo (eg) a DB engine, you'll want the "uplink" that lets you call code on your workstation from your app. (There's a three-minute demo of us controlling a Raspberry Pi that way: https://anvil.works/blog/uplink https://anvil.works/blog/uplink).
- wslh 10y agoGreat! What features are you planning to add in the near/long term? I think it would be great to have ready to use access to web APIs, separate the front-end from the back-end, and target other popular programming languages like Node.js. I recommend to do a "Show HN" to get invaluable feedback from HN users. I know it can be painful but listing your competitors will be useful.
- meredydd 10y agoMore features...where do I start? Certainly more service integrations (there is already ready-to-use integration with several APIs, including Stripe, Google auth/drive/sheets, Active Directory for corporate users, etc, but there's always more to do). There's also a nifty DB upgrade on its way, as well as a beta of push/pull Git access to each app's source (that one's live today - there's a Git Access button in the IDE). Ultimately, though, it's all being driven by user feedback now. We deliberately chose Python because Javascript (language and ecosystem) is a dumpster fire whose weaknesses keep getting papered over with a new framework-of-the-week. (Fun fact: The median modern web app is written with five programming languages and three frameworks. Take a moment to soak in how nuts that is). Python lets us implement simple, idiomatic APIs for things that would require multiple frameworks, nested lambdas and async hell in JS. (We translate into async hell in the compiler :D) Expect an HN post or two before long...
- mattmanser 10y ago
- nulagrithom 10y agoInteresting point. I think that's the first half of the presentation: "we have taken the entire messy and complex world of telephony..." Twilio _chose_ and solved a problem that sucked. If your product doesn't solve a tough problem, it will be almost impossible to get the same "wow" factor that Twilio does. Maybe the answer is that less obvious applications will simply be at a disadvantage right out of the gate.
- nbadg 10y agoI think it's important to point out that not only did Twilio choose a great problem to address, it was (critically) also one that a large audience already understands is very difficult. There are plenty of equivalently "valuable" problems to solve, which aren't as easy to communicate effectively, because most people lack enough domain-specific knowledge to understand the difficulty of the problem. This, I think, is the core truth behind the oft-repeated observation that you should "pay attention to the startups with a few customers that absolutely LOVE their product". Not all valuable problems are ones that a general audience is likely to comprehend, but when you narrow it down just to the audience that does, how do they feel about what you're doing? Put differently: the Twilio demo is so effective not just because they have a very good problem, but because it's an exceptionally common one as well. They have an impressive solution to a tough problem, sure, but they laos did a very good job aligning "the people who have this problem" with "the people listening to this demo", and that's what makes it great.
- strangetimes 10y ago> I would be impressed with a tool to quickly design a web application in the same way Visual Basic did 25 years ago instead of talking about Bootstrap, Foundation, AngularJS, React, etc. It's called ASP.NET Web Forms. Version 1 was released in 2002. Demos of it back then were quite impressive.
- wslh 10y agoI tried it circa 2007 with Sharepoint and it was a pain in the * to use the web components/AJAX. It was the first time I used Sharepoint for development so take it with a grain of salt. Could you please point me to some modern demo?