Friday, October 23rd, 2015 by Servage

Awareness of your users' needs is the starting point for any improvement. This information can be gathered from multiple sources, e.g. satisfaction surveys or questionnaires. Instead of being gathered specifically, it could also be collected during more natural interfaces with customer, e.g. during support requests. However, it is also very meaningful to gather this information systematically based on users' behavior, and nothing is more clear than raw statistics data from users' behaviour on your site.
You may already be collecting this type of information, but are you also using it? Really using it? Meaning that it is nice to look at visitor numbers and most popular sites on an analytics page, but what does it ...
Sunday, October 18th, 2015 by Servage

The ability to send emails from within your web application is essential to almost any website or system. This rather trivial task is sometimes complicated by relatively unreliable libraries and unstable sending methods. If you have been around PHP for a while, you will probably remember the old days using the native "mail" function in PHP with Sendmail. Fortunately a lot has happened over the recent years, and great options for easy email sending (and receiving) have been well adopted in most frameworks.
Laravel includes an email sending API built upon the common and very popular Swift Mailer library. It provides all the basic sending capabilities and is wrapped into a nice object ...
Friday, October 9th, 2015 by Servage

We have recently presented Ember JS as one of the modern frameworks for building great web apps with current standards and technology. Today it is about Angular JS, which is a great alternative to Ember JS. Both frameworks have great capabilities and it would not be fair to focus on a single one of them, because there is no good reason why one of the two frameworks should be better than the other. Smart people say you need to choose the right tool for the job, and when it comes to Ember JS and Angular JS you have two great tools that can solve hard jobs. You will likely be happy with ...
Monday, October 5th, 2015 by Servage

Working with websites in different languages requires a system that can handle content to be displayed depending on a language setting. This setting is usually derived from the user's profile settings, the client's browser preference, or maybe the remote IP address country. Either way, as soon as you handle more than one language, you need to deal with a dynamic display. Actually it pays of to implement localization even for just a single language, because the overhead by implementing localization is usually relatively small. However, implementing localization afterwards can be a major issue, because all the code needs to be revisited. It is much faster to implement it from the beginning.
Laravel ...
Recent comments