Usually the de-facto standard to get notifications about important events from your web applications is email. Emails are not really an ideal tool, but they works (soon I will have a big news about that).
Sometimes you don’t need much information about a specific event, you just want to be notified that it happened. A good example of this case is user’s registration.
Probably you don’t need to know much information about your new user (you have valuable information in your database afterall), you just want to know that someone sign up.
Recently I found (and I started to use) Pushover, it’s a tiny application (available both for IOS and Android) to which you can send all notifications you desire.
Integration is really simple, you have just to do an HTTP request with your notification’s data and you will get almost instantly it on your mobile.
Easy and useful!
If you are looking for a fast way to integrate it in your ruby app, I created a little gist with the class I wrote for it. https://gist.github.com/simo2409/3121ce8a4e6235b028adComments
Today it’s very common to use fonts to include icons and small images into web pages. At the beginning everyone was excited by this possibility but not many people thought about cons.
Consider one of the most known font for icons FontAwesome, it contains around 350 icons packed in a easy-to-use font file.
As said, including FontAwesome in your page you have access to over 350 icons whenever you need them but probably you will not use more than some of them on your great site.
Let’s suppose you are using 10 icons, this means you are forcing your users to download 340 icons (still packed in your font file) which will never be used. It’s wrong.
The right approach would be to decide which icons you need and to create a custom font file which contains all-and-only icons you are going to use.
To help you doing this (boring) process, http://fontcombiner.com/
I have still to try it, but it looks great and it will drive you and your user to a better (and faster) user experience on your website!Comments
On 7th of April a bug in OpenSSL became public, friendly called “Heartbleed Bug”. In IT world it’s not very rare to find bugs on many layers of an infrastructure. It’s generally a good thing because finding bugs the overall security increases providing a more secure IT world.
In last 2 days there was much much information related to this bug, partially because OpenSSL is a very critical part of anything considered “secure” and partially due marketing.
Internet is generally considered (correctly) an insecure world but thanks to cryptography (which OpenSSL is a very important key) the web became far more secure than before. So it’s important that every people involved in IT know about the bug in order to fix/update what needed.
The problem about this bug is that it was used to make marketing. In last 2 days I received tens of emails from all web-service providers in which they claim/announce they are fixing/already fixed the problem on their end.
If on a perspective it’s good to inform users on some critical fix done on your service, on the other side I’m asking myself why this bug was so advertised. A bug in a webserver or in a database is not less important nor less critical than this one, but nobody alert you when update used db or web server.
I’m for an open, shared and transparent communication (and in general honesty) with customers, but I think that the Heartbleed bug was really treated in a terrible way by everybody and not “by error” but “by marketing”.Comments