I get it's a piece of history, but how do you monetize this? Convert it to paid software? Streaming service subscription?

Winamp has a 10,000,000 - 50,000,000 installs android app, that opens up a lot of possibilities.

What kind of add revenue can you get from that user base?

No idea but I don't think display ads would be that great since it's mostly passive software. I would think there are better ways to monetize it - premium enhancements, amazon/itunes referrals, cloud backup/streaming your library, even just selling it for a buck ... 'best' trumps 'free' a lot of the time on mobile.

I swear I was reading a different HN thread on this topic yesterday or even today, and the very idea of paying for a music service was considered extremely offensive.

I pay for rdio and SubSonic. Granted my subsonic license is grandfathered in from before the developer changed to a subscription model, but the point remains.

From linked articles it has ~6mm in revenue already. Clean that up, optimize and then spread out.

It already was paid software! (Even if you didn't actually pay for it)

How did that work out?

AOL is a publicly traded company. They have "responsibilities" to their shareholders to grow. How a private company of 20 can handle a product like Winamp is drastically different than a company with 5000+ employees. Flexibility, reaction speed, etc.

Actually, they have a responsibility to endeavor to turn a profit. Growth at any cost imho comes from MBA's who want to spin the lottery wheel and cash out stock options.

As well as it did for WinRar I suppose.

Depends on who you ask.

Clearly there is a pain point with PostgreSQL and GUI front-ends. Wish I could see the site.

Honestly I found the sooner one gives up and just uses the command line, the better.

Indeed. I really have no idea why so much energy is spent on GUI tools.

What do these things provide that one can't get from the command line, I wonder?

I guess being able to see a whole bunch of things at the same time is useful, plus never having learn much SQL, plus being edit things by clicking on them.

[I just realized that my comment may have appeared very harsh, specially from the authors' point of view. My apologies to them, I was _very happy_ to have a good GUI when I started working with databases]

@antihero : Seeing things does help, but in my experience, using scripts and the command line is faster for developpement, because a lot of code can be reused, which is not the case with clicks.

I was being too restrictive though, a lot can be done with a GUI, of course.

Only one improvment for me: It should bounce at the top and bottom!

I think Apple has a patent related to iOS' "snapback" scrolling and that's why Android switched to using the awkward "blue glow" scroll effect.

They don't necessarily even need to make a phone call. Once I heard the news I sent emails to about 10 lead/senior developers.

no NYC?

AD60 - Brooklyn, NY (http://www.ad60.com/jobs/)

We build mobile apps for iOS, Android, and Windows Phone 8. We need mobile developers and web developers.

Most recently we've built apps for Songza (https://itunes.apple.com/us/app/songza/id453111583?ls=1&...) and YouSendIt (https://itunes.apple.com/us/app/yousendit/id442140135?mt=8)

For one of my apps it says that I'm not using a production ready database. I'm using Amazon RDS. How well will the DB add-ons integrate with this check?

Hey, Heroku engineer here. Can you shoot me an email at jonathan [at] heroku [dot] com and I can take a look?

IIRC you actually have to remove the Heroku postgres DB for it to pass if you're running RDS.

This is correct. If there are no Heroku Postgres DBs, the test is skipped. If there are any, the test only passes if there is at least 1 production-tier database.

How about an option to frame it?

Agreed. Although, as a person who runs an agency, I do get a lot of emails a day from freelancers. So, you should try to stand out by showing your best work up front and be a real person. Don't try to sound like you're a team of 12 by saying "we" and attaching your company logo to everything. Simply say...

"My Name is protoweek and I really like what you guys are doing. I especially like your app XYZ. If you need help on a project I'd love to work with you. Here are the last three apps I've published. If you need an invite code let me know.

http://www.protoweek.com/app1 http://www.protoweek.com/app2 http://www.protoweek.com/app3 "

Something as simple as that usually gets my attention.

None of us will know the complete depth of their relationship, but TomTom shouldn't be so removed from this PR. What they should have said is "Although Apple provides additional layers of functionality on top of our map data, we've reached out to Apple to help support in fixing these issues."

That sounds a lot nicer than "it's not our problem"...