I wish the press would do the responsible thing and use the proper words for those things: "corporate raiders".
Giving into establishment's newspeak is not doing anyone a favor. And let questionable people do the toxic thing they do (destroying companies for his own interest) while feeling good about themselves.
For now, I chose to keep away from any media that uses those lying words (such the ones one would use to cover up for torture, bombings, etc).
I go out a lot (in my home town, and even more so in holidays), and I'd love to have an app to give me suggestions of events (special nights, museums, openings, and such).
Why was it a bad idea ? Have brandond and al. research the market ?
Having worked on a local events app in the past (which I ended up abandoning), I have a few thoughts. These aren't necessarily unsurmountable, but they were sticky points:
- Event database curation doesn't scale very well. If you want high quality and accurate content, you're either going to need to have people double-checking stuff or come up with some nice algorithms to pre-filter it.
- Event entry is a hassle. At the start, you're going to be entering a LOT of the content by hand. This is pretty normal across a lot of different types of product, but with event data, the data has a very definite shelf-life. As soon as the event is over, you've lost a piece of data and you're going to need to replace it with something else.
- Chicken & egg: when you haven't grown to be the place to search for events in a city, you're not going to have people entering events for the city (e.g. people who work at venues who want to advertise their events). There are so many different apps that advertise events for you, and putting events into all of them is going to pretty onerous.
- Facebook: for a venue, or a band, Facebook is a super easy captive audience. I follow venues I like on FB, and they advertise all of their coming events right there. That's your competition.
- Reasonably high cost to drive traffic. If I recall, we were paying somewhere around $0.25/user that came to our site. We got decent inbound traffic, but almost no sign-ups, and even fewer self-posted events.
- How do you monetize it? Your two big competitors are Facebook (free for posting events) and posters stapled to telephone poles (25¢/poster to print it).
Thanks for your feedback. This is very interesting.
> Your two big competitors are Facebook (free for posting events)
Facebook is not exactly a competitor because it's a walled garden. So you have to be part of the right groups or be suscribed to official pages to get events.
It don't know about you, but all this facebook overhead is starting to bore me.
I love salsa, hip places and fancy. I want the best events for me NOW.
I love dive bars, cheap beer and sweaty rock. I want the best events NOW.
> - Chicken & egg:
If you can't populate your event base with pre existing data, you may have a chicken/egg problem.
Unless you have some magic crawler technology...
I'd love to have a access to a event central database that curates events for me matching my taste and previous choices.
I could pay a flat fee for a mobile app that could do that.
And I wouldn't mind it having ads for other places/events that could suit my taste.
I have a hard time imagining that events curating is not a real problem.
Finding new places and fun events to go to is actually a pain.
Is it a monetizable pain ?
The linked article implies that Paul Graham thinks that this is not worthy of a shot (or a second shot).
Is it not monetizable enough ?
Is it a nut too tough to crack ?
I wonder what the reasons are (I wish I have more research on the subject).
Well, this problem got me thinking.
If you want to keep talking about it, here's my email name.is.carl (@) gmail (you know what)
Excel is a tool.
The major problem is the dimwits (mainly in suits) that use Excel instead of thinking.
Anyone can make a decision if $A$1 > $B$1 + $C$1.
When an Excel formula is doing the thinking for you, this is a bad sign.
For you as a person.
And for your job that will be shipped some day.
To India (no offense to the nice chaps over there).
Or to some ERP module (no offense to SAP).
Agree on India, but SAP? Nahh, the time they want to do that the guy that put the Excel file in place in the late ninties already had his job shipped to india a couple of years ago. And now there's nobody left who understands what this excel file is doing.
And putting that into SAP is way to expensive, as long as you can still port the Excel file to Office 2010, that is. If you can't, you'd have to ship the company to India...
I second that. As javaists are concerned, Play 2.x is not a good thing : bigger, slower, more rigid and with a lot scala dependencies/idioms you don't care about.
Forking Play 1.2.x could be a solution (and maybe remove the python console. After all that's a java framework)
Or.
Or one may use the extensibility of Play 2.x to remove the scala parts javaists don't want.
It shouldn't too hard.
As the silence of the ISPs.