In today's software world, we have no shortage of choices when it comes to developing applications. Even in the limited scope of Windows Phone development, there are choices galore. Do you develop a native Windows Phone app? Do you take a hybrid approach? How about Xamarin? WHAT DOES IT ALL MEAN!?
To help you wade through this complexity, in this article, we'll take an in-depth look at one of these approaches: hybrid. Specifically, we'll look at why you would want to build hybrid, and how to do it. Let's start by looking at where hybrid can be a good fit.
There are 9 areas that every software development team has to deal with in some capacity. And if not done carefully, your software will be vulnerable to failure to some degree. Learn what they are and how you can mitigate your application's risks.
In this post, Jeff shares the code, slides, and video recording from our webinar covering how to use the Telerik Platform with Visual Studio. He answers all of your questions, and provides some helpful links along the way for those looking to get started with the Telerik Platform now.
Hybrid applications are unique because they run in a "browser" but without a server component. They also aren't expected to look and behave like a web application. The unique constraints on hybrid applications require a good code structure in order to be able to productively build maintainable mobile applications.
Recent coverage in the Bulgarian business press on Telerik's selection as AonHewitt's
2013 Best Place to Work (Medium-Sized Company) in Central and Eastern Europe
We are open sourcing JustMock Lite and giving it to the community. We are giving you the chance to see and improve upon the JustMock Lite source code and share your changes with others. Now you can easily add any functionality that you need and want. We are sure you can make JustMock Lite even better.