Showing posts with label programming. Show all posts
Showing posts with label programming. Show all posts

Wednesday, April 23, 2014

The Time-to-Market Advantage in Mobile Application Development

As a visit to Damnoen Saduak Floating Market of Thailand will confirm, time-to-market and distance-to-customer are distinct advantages in business. 

It is difficult to know which came first: the customers with their curiosity and pocketbooks or the merchants with their bamboo and palm hats and colorful produce, but they are certainly mutually drawn to one another. People do not come here because the prices are cheaper but rather because the produce is fresh, accessible and sold in a convenient and interesting way. In bygone days, the vendors would paddle their boats on the waterways buying, selling and trading fruits, vegetables and other goods all across Bangkok’s canal system.  The canals were convenient, the boats efficient and the coverage of the canals was pervasive across all of the city. Where am I going with this?

Today’s mobile networks are pervasive, mobile apps are interesting and they can get to customers first, right where they are.

When it comes time to build mobile apps that can reach customers, time-to-market has more to do with the ability to develop mobile apps that run on multiple device operating systems and integrate to back-end business transaction systems in an efficient and agile manner. Distance-to-customer is the advantage that mobile apps have because they reduce the transaction distance between you and your customer to zero. Your ability to sell to customers is no further than the palm of your customers’ hand.

But quite frankly time-to-market is often a disadvantage of mobile apps because of the long lead times required to develop mobile apps using native platform development tools. That’s why when we see a platform that claims to marry the advantages of rapid development techniques, pre-built integration solutions and a capability for cross-platform mobile smartphone and tablet deployment, we have to pay close attention. Faster time-to-market for mobile apps requires a smarter application platform.

 Most development approaches fall prey to the time-quality-cost triangle and suggest that you can choose only two of the three beneficial qualities: less time and more quality or less time and less money or more quality and less money. The prevailing wisdom suggests that you cannot have all three. But frankly this popular dilemma is based on the preconceived notion that all approaches require a fixed effort.

What Magic Software initiated in the 1980s with the notion of a rapid prototyping platform for creating business applications carries forward today into some fairly slick and sophisticated technology that still gets overlooked far too often by the mainstream computer programming community. The benefits of an application platform can be found in the fact that it breaks through the problem of fixed effort. Platforms have built-in solutions. They allow for very rapid results by leveraging common application development requirements in an underlying solution set or platform.

Daniel Coyle, author of The Talent Code says: “Baby steps are the royal road to skill.” As I have said before: “Regardless of whether you use agile or scrum project management methodologies, early and frequent results are essential. Too many projects are cancelled midstream simply because their progress is shrouded in mystery.” An application platform gets you to those early victories and propels you to frequent wins that will keep executive sponsors engaged to completion and asking for more.

Native development suffers in comparison to Magic xpa application platform development for a number of reasons. First. More tools are needed. This is not opinion, this is fact. With native development you need a server-side language and deployment methodology and a client-side language. Furthermore, the client-side languages are different: Objective-C, J2ME, J2SE, etc. Because of the extra effort required by these tools, more programmers are assigned to a mobile app development project. While  environmental complexity increases with native mobile development, the Magic paradigm of platform based metadata development remains constant: one tool for all requirements – server-side and multiple OS clients.

To understand the absolute significance of this, one needs to consider the COCOMO II Model of software estimation perfected at the USC Center for Software Engineering. (Go Trojans!) The COCOMO II model can be simplified as follows:

                      Effort = (Team) x (Tools) × (Complexity)(Process)

As you increase the number of programming languages needed (tools), effort increases. The concept is fairly simple. As you increase the number of developers (team), effort increases. And as you increase the functional requirements of the application to be delivered (Complexity), effort increases. The relationship between these three components of effort is factorial.

Those restaurants along the canals of the Damnoen Saduak Floating Market want their vegetables really fresh. For really fresh mobile apps, consider the Magic xpa Application Platform.


Wednesday, May 1, 2013

How Magic Software Beats the DIY vs. Off-the-Shelf Dilemma for Logistics Service Providers


To remain competitive, Logistics Service Providers (LSPs) must have deep knowledge of both their industry and their unique place within it. They must know the complexities of the logistics sector and the custom business practices and processes that make them stand out with a defensible competitive advantage. Automating your proven approaches to everything from customs and tariffs to language, culture and partnerships can accelerate your ability to offer competitive services, business practices, rates and solutions for your customers.
The commonly heard debate between buy vs. build overlooks a third, better option: co-create. The problem with packaged off-the-shelf (OTS) and Software-as-aService (SaaS) applications is that they deliver bland generic capabilities that simply put you at par with last year’s thinking about how-to run a logistics company. Whatever capabilities you obtain in a packaged application are also available to all of your competitors. The problem with do-it-yourself (DIY) programming based on commonly available languages and tools such as Java and C#/.NET is that it puts all of the development burden on your IT department and this often results in project failure.

Magic Software takes an approach to custom development with LSPs that avoids these problems. First, we leverage an application platform on top of common technologies like .NET that will literally save years of development effort. Our uniquely responsive development environment allows us to deliver functionality at the speed of business. The peculiarities of software design are managed automatically by our underlying platform so that our programmers can focus on your logistics business logic. Second, because we manage a highly-trained and motivated team of developers, your IT department is not burdened with recruiting and retaining delicate and expensive human resources.

The primary focus of an LSP business is on the global shipment of goods and even more importantly on customer satisfaction and loyalty. Magic Software is in turn focused on the business of delivering quality software tailored to your business and on your satisfaction and loyalty.  For this reason, Magic Software overcomes the dilemma of choosing between DIY and OTS by doing the work in collaboration with you so that you remain focused on what you do best: logistics.

Magic Software maintains a team of highly-trained consultants, project managers, and developers that can be deployed immediately on development of your applications. We take the hassle out of managing a team of developers and we help you avoid the paralysis that comes with being handcuffed to an OTS package vendor. OTS vendors in the logistics industry are notorious for resisting changes in their packaged applications because it would have ripple-effects across all of their customers. They can’t provide you just what you want precisely because other companies take a different approach. The harder you push for feature requests that provide you with unique competitive advantage, the more likely you are to run into resistance and be presented with highly inflated feature request costs.  And if you do succeed in obtaining the feature you want, you run the almost certain risk that the OTS vendor will rollout this feature to your competitors. You’ve been placed in the untenable position of financing innovation for your competitors!

OTS vendors will try to sell you on the idea that their packaged applications deliver superior business practices that are ahead of what can be created for you. But the reality is packaged applications take the least-common-denominator approach. There is nothing special or uniquely competitive in their approach because it must be designed to please the average company. We all know that in the logistics industry, average companies fail.

Because Magic Software works with a wide variety of customers in the logistics industry from global brands like UPS and DHL to small and midsize 3PLs, we know the industry and can provide experienced consulting to help you brainstorm and design best practice approaches and more importantly approaches that deliver truly innovative value.


Due to our flexible application platform and our experience designing software, we take a software architecture approach that maximizes reusability and flexibility. This requires experienced logistics development teams with an understanding of service-oriented development of applications that deliver just the right level of business process granularity to maximize repeatability and flexibility.  And because our integration platform allows for loosely-coupled approaches to integration, there is little or no coding required to leverage pre-existing systems and business practices.

OTS vendors also take a honey-trap approach to costs by hiding their lifetime total cost of ownership in monthly or annual fee structures. Careful TCO comparisons between custom development of your perfect, “dream applications” by Magic Software and packaged OTS applications that deliver normal average value make it clear that the TCO analysis is heavily in Magic’s favor.

It is true that software development has risks. These risks are overcome by outsourcing the development of your application. You can outsource the development of your application to an OTS/SaaS vendor and get the same average system as everyone else or you can outsource it to Magic Software and get a custom-designed superior solution that is easier to maintain and faster to adapt to changes in the market. The up-front cost is more than justified by the long-term benefit and up-front costs can be financed as needed.

Flexibility and responsiveness are vital to remaining in compliance. The regulatory environment of the logistics industry changes frequently and being held-hostage by the feature request process of an OTS/SaaS vendor can literally bring you to a halt in the face of new regulations in local markets. Magic Software’s long track record of helping literally hundreds of companies adjust their systems on-time for such imposing regulatory schemes as Nota Fiscal Eletronica (NFE) in Brazil is only one example of how Magic Software is more responsive than OTS/SaaS solutions to regulatory requirements, especially in new and lucrative emerging global markets for logistics.

OTS/SaaS vendors expect your business to remain in place until they get around to making changes based on an arbitrated average of user requests. This can kill your business and expose you to massive risk. Working with Magic Software, you get the features and compliance solutions you need when you want them.

So the next time a vendor approaches you with the suggestion to purchase their SaaS solution or packaged application, ask yourself ‘do I want to be average?’ Can you afford to be behind the curve and slow to respond to changing global business requirements, can you give control of your most vital assets, your ability to automate the delivery of logistics services to a company that is offering that same average value to all of your competitors in their next phone call?



Tuesday, October 23, 2012

Keep or Toss: Is ActiveX Dead?





Opinion on ActiveX varies. Some say ActiveX is dead, passé, an old technology with no future relevance. Others say that so much has been invested in ActiveX that it is economically infeasible to adapt to newer technologies such as .NET, RIA, JavaScript and HTML5. 

I say that the beauty of the Magic xpa Application Platform is that it is economically feasible to adapt to these newer technologies. And well, yeah, if you don’t want to then you don’t have to because you can wrap your ActiveX.

Having said this, my recommendation is to leave ActiveX behind in favor of new RIA clients. You don’t have to abandon ActiveX, but you should, and you will still be using 100% of your core business application logic.  

Trying to keep ActiveX in today’s modern operating system environments is kind of like trying to preserve a function key interface on an iPhone. Yeah, you could do it by creating graphical representations of F1, F2, F3, F4 and yes the holy F5 key on the touchscreen of the iPhone, but why? 

There is a better future and it’s already here. Reluctance to change is a natural human reaction and it seems to increase in some people as we grow older. But the beauty of our tradition in the Magic community has always been that it is easy to adapt to new technology paradigms with Magic xpa Application Platform. A metadata driven platform makes it easier to transition to the newer fully .NET native Magic xpa Application Platform. 

Because let’s not forget: the road to .NET is Magic!

Tuesday, November 2, 2010

Did you vote for your favorite Governor?

Vote uniPaaS: A Development Environment with Extensive Resource Governance

Today was Election Day for the next Governor of California. As I write this, I do not know yet who won the election in the contest between former Governor Jerry Brown and eBay pioneer Meg Whitman. Whether discussing public policy or software development, governance is important.

In software development, good governance helps you meet challenges in managing resources and artifacts. A developer needs to keep track of all sorts of resources including variables, forms, expressions, models, formats, messages, programs, Web services, etc.

In most IDE’s, developers have to decide on artifact identifiers which must be unique, and once defined they cannot be modified. This forces extremely strict guidelines essentially putting the developer in a straightjacket. It also involves a lot of creativity and forces developers into their own fantasy world. This aspect is difficult to automate while maintaining program legibility. It is also common that naming conventions change as projects mature and grow, and the ability to implement new artifact naming for existing applications is a very rare luxury.

With the uniPaaS application platform, a resource and artifact governance framework is built-in, with highly automated artifact management. Developers do not need to provide resource identifiers but only resource names (descriptors). Resource names can be modified anytime, and any modification is propagated wherever the resource is referenced. This enables much easier resource management and easy maintenance of very large projects.

Furthermore, all the resources of a uniPaaS project are maintained in an integrated set of repositories, facilitating the automation of their creation and management. In addition, a number of third party tools such as Magic Optimizer are available to optimize and document these.

Another important aspect of the uniPaaS governance framework is the program transparency and legibility. Artifact descriptors can be as meaningful as necessary and can include any type of character. Coupled with standardized program structures, they make programs much more legible and maintainable even by developers who see the program for the first time.

Leveraging Magic Software’s rich experience with metadata driven development, the uniPaaS application platform provides abstraction capabilities that facilitate the design and development of complex applications and encourage resource reuse.

The development paradigm is declarative, event driven and service oriented. It is also a unitary one, meaning that the development process of RIA or Fat-Client applications is the same – there is no need to develop separately for a Fit Client, since the platform abstracts the Client and Server partitioning. Fitness is an important consideration in governance.

By the time you read this, you will probably have heard the news as to who was elected to succeed the very fit “Gubernator” Arnold Schwarzenegger as Governor of California. One thing is for sure at this moment, you cannot go wrong when choosing uniPaaS for application development and deployment.