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
A lot of companies have just the staff necessary to take care of the day to day tasks and problems. It's only natural considering the shortage of developers and the need to keep costs down. To innovate, it's necessary to have resources dedicated solely to develop new features and products. Resources that are not held
In previous blog posts we've written about minimum viable product, making sure your product actually fills a need (solves a problem) and how to identify your customer. The time has come to talk a little bit about prototypes. The message of this blog post is, in short, don't do it! Disclaimer: we're talking about software
Most of us don't want to take a product to market unless it's perfect. It's understandable but a mistake, because no product will ever be finished and perfect. It also keeps a lot of great products from reaching the market. In order to finance that stroke of genius that is your business idea you'll need to