Limits of the FREE version

It wasn't easy for me to decide how limited the FREE version should be. Sure, I want users motivate to pay at least something, but I don't want to oust them completely.

I hate few things in desktop apps, even I understand their purpose. I hate grayed out menu options, just because PRO version has it. I hate even more the unavailable option isn't distinguished and I learn I have to pay first only after I click on the item.

I can live with some promo upon startup or closing the app, because usually I don't do it too often. But only if it's in a "polite" way, when I don't have to hunt the closing window nor close automatically opened tab in my browser.

I like x day trials, when the app works fully, but my problem with trial versions is, that it has to write the start date somewhere, obviously, and this thing stays on my computer even after I got rid of the software, again - obviously, but after that it's just garbage.

I hate online DRM, even it solves the problem of crap residing in my computer.

So, what DO I like? I like when the only limitation is I can't save my work locally, but I'm freely able to do anything it offers. After purchase there is a encrypted file with the license and this way I will do it with QetriX.

And some polite ads for FREE users, even many of them know how to block them. I believe users can live with tasteful and just slightly disturbing (not by contents) ones.

Semantic Dictionary

One of my "unfinished businesses" is a semantic dictionary. Basically it will be a gigantic database of all words in all forms (as entities) and they'll have a set of attributes and relations between them, defining what kind of word it is (subject, verb...) and what relations between other words are (synonym, antonym, the same word in different language...).

I expect the primary usage in semantic search. The search engine will use some kind of universal meta language, to which all queries in natural languages will be transformed.

I can't say how (and if) it will work exactly, it's just a thing I've been thinking of quite a long time. I'm aware there are some nuances and pickles (like the same word with different meaning not only in different languages) or how to deal with phrases in search queries (my former thought was just to analyse word by word, but It's not that easy).

These are some of expected unknowns I didn't make any further research about and therefore I don't have comprehensive overview of it.

And, last, but not least, it will be a nice performance test :)

Moved wiki from Wikia

On Monday I moved our wiki from Wikia to our own system. Why? Well, Wikia is great, simple and intuitive. You can use many advanced features, but you also have to undergo ads and Wikia network. There is too much clutter for my taste.

Wikia was temporary for me anyway, but I thought I would migrate to system built on QetriX. Recently I decided to do some major improvements, so I didn't want to rush things. I already run few wiki instances on my own wiki engine, so I had no other reason to stay at Wikia.

I only had to migrate the current content (about 30 pages) and customize style sheet (CSS). I like it much more, than Wikia version, and also the URL is much nicer: wiki.qetrix.com. So take a look! :)

Google Glass

People say that New York City you can either love or hate, noting in between. From buzzing around Google Glass I can say the same about this gadget. Even though I find myself on the side of "hate", as I see it as a major breakthrough into my privacy, from QetriX's point of view it's a major opportunity. It's exactly what I'm focusing to in this project - tiny pieces of important/interesting information on the go.

I can tell apart those opposing feelings easily, because my personal concern is about the built-in camera, whereas the opportunity is spurting from the head-mounted (or "heads up") display.

The true resolution of the display remains unknown, but for the apps Google recommends 640×360. There are also quite strict guidelines for creating apps, also made by Google, which may keep the environment homogeneous.

I'm working on use cases for small resolutions, because Glass is not the only such device. We're more hearing about various wearable devices these days, like bracelets or watches (Pebble).

Desktop App

When I was searching for inspiration thru AppStore, I found a great ToDo app, called Wunderlist2. I didn't need it, because I was already using Evernote for ToDos, but I like it's completely free and has mobile + web + desktop access - exactly what I admired Evernote for and what I was aiming at with QetriX.

But it was pretty neat. Like Evernote it looked the same on all platforms and unlike Evernote it featured beautiful desktop App. I was wondering how it's possible to achieve this look and my first thought was it's some kind of HTML5 wrapper. I knew Evernote was written in Qt and I made several apps in WinForms, but neither was an option. After a little googling I discovered WPF.

I came across WPF a while ago, when I looked for a simple way for 3D engine and I was playing with XNA little bit, but I thought "what the hell I would use this for" :)

WPF, like Android or ASP.NET, has GUI defined in XML and attached functionality in C# (in my case). I was overwhelmed by the GUI definitions, but fortunately I was able to figure out how the Wunderlist app is made, thanks to the WPF Inspector from CodePlex.

I don't rush with the app, but I'm glad I did these first steps and in the meantime I can think about the final product.