Live data from Hacker News

Lanyrd: From idea to exit – the story of our startup

blog.natbat.net

31–36 of 36 posts

Re: Lanyrd: From idea to exit – the story of our startup

#32
post #3

Natalie put a lot of work in to this (and we're suposed to be on holiday!). There's lots of great stuff in here - not just about the overall startup experience, but also advice on talking to press, raising money and building out the company.

This is a really nice writeup of the whole startup process. Thanks for this!

Re: Lanyrd: From idea to exit – the story of our startup

#33

>Over time he completely re-architected the app to have a UI that is driven entirely from the server and doesn’t need to go through the various app stores to release changes. So I'm reading this and wondering: this differs from a webapp how exactly?

There's more to a web app than the UI.

True, but the UI is the only part that defines it as a web app.

Re: Lanyrd: From idea to exit – the story of our startup

#34

Earlier quoted context omitted.

There's more to a web app than the UI.

True, but the UI is the only part that defines it as a web app.

You can also define a web app by the capabilities of a modern web browser, e.g., storage, network, graphics.

Re: Lanyrd: From idea to exit – the story of our startup

#35

>Over time he completely re-architected the app to have a UI that is driven entirely from the server and doesn’t need to go through the various app stores to release changes. So I'm reading this and wondering: this differs from a webapp how exactly?

Our iPhone and Android apps both use native UI components (table views etc) that are defined by data from the server, so we can ship new native-feeling features without compiling a new build.
Post reply on HN