Sitemap

It’s about time.

3 min readOct 9, 2014

So, about 10 years ago, I started using SmartLaunch, a net cafe management software full of promise! Compared to the competitors, it looked sleek, it had all the functions wanted and more. That was version 3.6 and we had to pay a hefty price for it back then.

The problems started right way. Bugs, bugs everywhere. It was worse than beta and had to spend hours on the phone calling some dudes in Denmark to get some often futile piece of help. Bugs small and big. For example, the biggest selling point, the ability to save the users’ savegame didn’t even work if the were larger than a few KBs (most were, even back then) and the client would hung. They did come with some updates, but they fixed small issues, and created some more issues.

A couple of years pass, and the come out with the much awaited v4, the version to fix everything. And it did fix those bugs, but introduced a whole new slew of them.

How do we call a software release that fixes bugs? Not a patch according to SmartLaunch, but a different product, asking us to pay everything all over again!

And we did. We were forced to pay for a new round of licences for what was basically a fix on their software. Still the server run on .net, still the client run a God awful uncustomisable flash app using the wrong resolution.

Somewhere between version 4.1 and 4.2, evidently the company basically changed hands, and the new management had great ideas!

  1. Leave the program suck. Seriously, its been years and it’s more unstable than ever.
  2. Focus on marketing. Polish the website, go blogpost crazy, and relentlessly spam anyone that downloaded the free trial.
  3. But the best part, the absolute cherry on the top: Make everyone that bought it (even twice) pay from now on, a crazy high subscription for it. Or else it stops working. WTF, seriously?!

All that was done under the guise of blowing a fresh air of cashflow in the company, that would mean developer manhours, that would mean a solid product at some point in the future. A few years have passed since then, bringing SL to v4.7 and this thing stinks worse than ever.

So why am I writing this? It is time. It is time to get off my ass and do something about this problem. God knows how many net cafes are there in the world, and the software to manage them is worse than awful.

~ Be the change you want to see in the world. ~

Starting now, my new all consuming side project is to make one modern, user friendly, rock solid, future-proof, net cafe app.

Get The Restless Admin’s stories in your inbox

Join Medium for free to get updates from this writer.

The idea quite simple:

  1. Built a networked app, that runs on a web server locally or online. Let it do all the database stuff and be the hub that maintains the connections.
  2. On the client pcs use a live webapp from the server, probably wrapped in a Windows & OS X container, that has an awesome html interface, dead simple to change instantly.
  3. On the admin(s), run a different interface of the webapp for admins, from the same server.
  4. Everything done with open source web tools and technologies, using as many ready-made frameworks to avoid reinventing the wheel.

How hard can it be? ☺

I was tempted, a lot, to start from the client interface, but in the spirit of ‘design is how it works’, I chose to start working on the server node.

And here comes the first big dilemma, which language to use for it? I’ve done some research and made up a short list of appropriate languages for the job:

node.js or Go

Django

Java

PHP

The problem is that they are all so close! The is no clear winner really, they all have their pros, and all of them have pitfalls.

So which one to code with for the next months is the question?