For many years now, the sweet spot of developer productivity and user experience was the fat client architecture. In this architecture, the information is accessed through isolated layers of apps. The first layer executes directly on the user's computer, while the other layers execute on the server. Most web apps are fat Embraced for over
In Part IV of this blog series, we dove deeper into the database as the puppeteer, as well as Puppet itself. In this final post, we’ll take a quick look at the “think” client and wrap things by helping you assess which approach makes the most sense for you when choosing the right database and
In Part III of this blog series, we continued to explore some of the key considerations when choosing the right database and framework for your real-time mobile app. Now, let’s dive deeper and take a look at the database as the puppeteer, as well as Puppet itself.
In Parts I and II of this blog series, we presented three possible categories that a typical real-time mobile app falls into, and started to take a look at the design choices for all three kinds of apps. Now, let’s continue to explore some additional considerations when it comes to choosing the right database and
In the first part of this blog series, we kicked things off by taking a look at the three possible categories that a typical real-time app falls into. Now, let’s start to explore the design choices for all three kinds of apps. Quick heads up before we dive deeper – the term “app” used throughout
If you’re a mobile app developer, I imagine you’re constantly feeling the pressure to quickly bring new apps to market and update them faster than ever before. The demand is only ramping up, with no change in pace on the horizon. Like many mobile app developers, you also most likely need a hard-working database behind
Last weekend I was honored to present at WebCamp Zagreb 2014 in Croatia. I would like to share some of my personal impressions of the event.
This past Saturday, I attended the Meet.js Summit in Poznań, Poland as a speaker. I gave a live coding presentation on building a simple single-page application (SPA) with Web Components.
Recently, I’ve noticed that Web Components has become the subject of many speaking sessions at IT and developer events – most notably InfoShare 2014 and Front Trends 2014. What was once a trend discussed in just a few online forums is now becoming part of every technology event!
This article is homage to jQuery – a library that once was a great boost for the productivity of thousands of web developers around the world. In the near future, the benefit of using it will drop as web developers start switching to the web standards, including Web Components.
Last week, I was invited to speak about Web Components at tech.3camp in Gdańsk, Poland. To my knowledge, it was the first presentation about Web Components in Poland!
Set of new technologies Web Components is an umbrella term for the set of upcoming standards for web development (see the W3C Web Components page). Each on its own is a useful contribution to the current toolset for a web developer.