Aggressive Development

What it is

Aggressive is a company developing apps and websites since 2009. Based in the Swedish capital Stockholm, crafting apps more furiously than ever.

What we do now

  • Aggressive is developing Feeds, an app to make it easy to keep track on news and noteworthy things around the web.
  • Digital business cards, to have an easy way to send your phone number to people (IRL) - straight from you phone to theirs (without downloading any apps).

What we have done

Aggressive Development has published 13 apps under its own name, and many more for other companies. More than 60 magazine-apps have been built for Swedish publishers, and here you can find those who are still active: Qiozk Solo Magazines.

feeds logo

Feeds is a news/rss app that streams webpages into your pocket. Feeds is the next application from the furious mind of Aggressive Development (that's me) - giving everyone easy access to news and blogs in the most elegant and efficient way possible. Everything streamlined in a convenient feed.

Sounds interesting? Read more about Feeds:

Latest from the Blog

Fetching articles...

Decision time for AutoDB

I have built the greatest database engine (on top of SQLite) that automatically turns your objects into tables. It even handles change-detection, auto-migration and syncing.

But what should I do with it? Give it away, sell it, or open source it?

The obvious choice is to sell it like a service, but this has been tried before and is a hard road if you aren't backed by venture capital. The most valuable part, syncing, is something I could sell as an add-on but would require a step up in the server department than what I have now. Probably I would need a full time employee only keeping tabs on servers (for starters).

The real question is: “Do I want to look after other people’s data for a living?” No, I don’t. I would like to develop the code, squash the bugs and fine-tune the algorithms, but not run it as a service.

Is there a middle ground? Sell it like a closed source framework and let the clients take care of their own servers? No, I don't think I could get anyone jump that train.

Open source feels like a nice thing to do. Give back to the community and perhaps also get some help or at least bug reports. The fear is that if successful, this turns into a massive unpaid job. And if unsuccessful, well then it’s just pointless.

It's decision time, so what should I choose? Let's insert a dramatic pause... Well, it's decided! I'll give it away as open source! Including sync for everyone to implement their own way to store data. Since I don't have investors (nor the time to devote into converting users) it won't become a big success. It might help someone and wouldn't that just be great?

Go here for all the details

Hire me!