Think about the major enterprise software systems around today. Several of them have their own very specific and closed platforms. They set their own rules, and have a very strong impact on the revenue stream for you the innovator, the independent software vendor. The business application world of today is dominated by a few giants.
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
Today’s solutions for keeping track of customers and potential customers are basically the same as twenty years ago. They are grouped under the name CRM, Customer Relations Management systems. However, these systems may soon be facing their dinosaur asteroid. The main reason for their risk of extinction is the fact that these systems were not
Choosing the right game to play is no simple thing, and most of us are affected by trends and what is talked about in the media. Many focus on consumer applications, especially mobile apps, partly because it's top-of-mind with apps like Spotify, Trello, Angry Birds, Pokémon Go and others. Another reason is, of course, that
The business application world of today is dominated by a few giants. If you want to take your application to market, you will most likely have to do it by building plugins for the giants and sell them through their app stores. But this leaves you exposed to the whims of huge closed platform corporations.
When multiple small tools band together, they can upend the status quo. This is today’s new collective app economy. In order for an app to gain traction in the enterprise, it needs the help of a whole host of complementary apps.
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
Technology comes before revolution. Always. And while not always obvious when first introduced, the importance of truly novel technology is not something reserved for tech geeks; in fact, it is and has always been vital for the evolution of the human race.
The latest and greatest from Microsoft when it comes to web development is Microsoft MVC. Although the acronym is new to many young web developers, MVC was actually quite popular in object oriented UI development in the early eithies. Back then, the best implementation did not only have one Model, they had two.