Developing software today involves a myriad of choices, and none of them are without some drawback. There is no silver bullet solution that fits all use cases, and every decision must be made carefully. Quite often I am asked “What tool should we use to build our application?” I don’t think that’s the right question, at least not initially.
Well, not that beginning, but in early days of developing non-mainframe based applications, the development ecosystem was a lot less complicated. There were just a few development choices, pretty much a single type of computer that we developed for, and for corporate line of business applications, hardware typically mandated by the internal support team. Even for companies developing commercial software, there were relatively few PC models and fewer resolutions. The two biggest issues that we faced was deployment and versioning issues, also known as the “DLL-Hell” problem. Occasionally, a vendor would release an updated monitor capable of higher resolution, and we would scramble to make sure our application could adjust and look decent enough on different resolutions. Sound familiar? This was our first experience trying to make our applications have a Responsive UI.
Sure, there were some hurdles that had to be dealt with, but that was nothing compared to what was coming next…
The early days of internet applications brought on a revolution of change for developers. Deployment issues mostly went away, but a host of new problems were introduced. Browsers handled markup differently, each of the vendors were adding their own custom features to gain market share, and we quickly learned that the simply dragging and dropping controls onto a canvas for the user interfaces just didn’t work. As code to detect browser capabilities became crucial to make the applications merely work, cyclomatic complexity significantly increased.
To sum it up, we had to make a choice - write applications that targeted the lowest common denominator (and resulted in very vanilla user experience), or write for a specific browser and force users to download and use the browser we chose. Neither option was ideal for the user or the developer, but there weren’t that many choices. Users didn’t have a choice to use internal line of business applications, and external applications were still mostly brochure ware.
The browser issues eventually settled down significantly with the browser manufacturers playing nicely together, and frameworks like jQuery helping minimize the effect of browser and DOM differences. But if you thought the age of the browser was disruptive, it didn’t compare to the onslaught of the mobile era.
Once the browsers settled down and became easier to manage, there was a new change that turned everything upside down. Mobile devices (initially phones and then tablets as well) hit the consumer market and took off like wild fire. Soon mobile browsers became a significant portion of the user base for our internet based apps. The outcry from users accessing sites from their mobile devices that were designed for desktop browsers was loud and strong. Companies scrambled to find a solution, and many took the route of creating another site specifically for mobile (such as “http://m.mysite.com”). By re-routing devices using a mobile browser to the “m” site, the user experience (for most) was improved because they were brought automatically to a dedicated site customized for the mobile experience.
The number of devices keeps growing with more and more sizes, resolutions, and capabilities. Users are demanding better and faster apps as well as more appealing user interfaces. Companies are fighting for attention in a market that has an extremely poor signal to noise ratio. There is no a silver bullet that will solve all of you problems.
With the multitude of devices, form factors, and capabilities, developers are constantly asking “What’s the best tool?”. While this seems like the right question, it really isn’t.
The first thing every developer should do is ask the right questions. It’s not a question of technology choice – at least not at first. A major trap for developers is latching onto a tool like it’s a hammer and then assuming everything is a nail. The best craftsmen have a set of tools, and know to apply the right tool to the right job. What is the purpose of your application? What is the audience? How will your users get your app? How will they get updates?
Of course, those few questions aren’t nearly the extent of the discernment that needs to be completed before a technology platform is selected and development started. At the end of that process, you must choose the correct tool for the job. Mobile or Desktop? Native, Hybrid, or Web? The best applications fit the needs of the users as well as the needs of the company sponsoring the application.
You’ve done your due diligence, asked the right questions, studied the market, and you are ready to build your application. Regardless of your approach or choice of tooling, Telerik can help you get there faster and more cost effectively. With an incredible selection of User Interface controls spanning Web, Hybrid, and Native development, we have a set of tools for you.
UI for ASP.NET WebForms
If you are a .NET WebForms developer, Telerik UI for ASP.NET Ajax has over 70 controls to help you build an amazing website significantly faster. In addition to increased speed of development using our ready for production controls, the UI for ASP.NET Ajax provides many benefits, including light-weight rendering, touch and mobile support, and seamless UX across browsers, plus much more. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/products/aspnet-ajax.aspx.
UI for ASP.NET MVC
ASP.NET MVC developers can leverage Telerik UI for ASP.NET MVC to build a seamless UX across devices and browsers. Featuring over 50 UI widgets with server and client side APIs, a responsive UI, and ready for touch, UI for ASP.NET MVC can greatly enhance your ASP.NET MVC application capabilities and significantly decrease your development time. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/aspnet-mvc.
Kendo UI Web
Kendo UI DataViz
Developers who use PHP can easily work with Telerik UI for PHP via familiar server side programming. With over 40 UI widgets, rich views and models with MVVM support built right in, and a responsive UI, it’s a complete web development framework. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/php-ui.
Java server side programmers can use the Java JSP framework to seamlessly configure and work with Telerik UI for JSP. Supplying responsive design, MVVM support, over 40 UI widgets, and much more, it’s everything you need to make your Java web applications come alive. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/jsp-ui.
Native applications offer the richest possible experience for user. Full access to the device hardware, off line capabilities, and the full power of the processor and memory capabilities. Whether the target device is a PC or a mobile device, native development fills a vital part of the application ecosystem, and just like with developing web applications, Telerik is right there by your side. Each suite is built from the ground up in the target platform for the highest quality and the highest performance. Not ported and shimmed, but 100% native development.
Windows Phone 7 and Windows Phone 8 developers can enjoy the Telerik UI for Windows Phone contains over 50 UI components as well as design templates, application building blocks, image editing capabilities, and integration with Telerik Back End Services. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/products/windows-phone.aspx.
Windows 8 developers can enjoy industry leading controls in the Telerik UI for Windows 8 suites. Whether developing for XAML/C# or HTML/JS, the UI for Windows 8 controls are built natively from the ground up to maximize performance and virtualization capabilities. Perfect additions to Enterprise and consumer app, the controls are store ready, designed for touch, and come with Telerik Offline Data Storage, the most advanced for Windows 8. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/products/windows-8/overview.aspx
iOS developers can enjoy additional UI interactions not addressed by Apple’s default UI library in Telerik UI for iOS. All controls are constructed using Objective-C, completely compatible with native app objects, and include animations, and easy to use API, and more. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/ios-ui.
Android developers can use Telerik UI for Android to fill gaps in the default UI library. All constructed using Java and completely compatible with native app objects, they contain responsive controls that adapt to the wide variety of android devices as well as a familiar and easy to use API. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/android-ui.
Windows is still the most popular operating system, ranging from Windows XP to Windows 8. WPF (Windows Presentation Foundation), WinForms, and Silverlight can provide rich and powerful applications for users of Windows (and Windows 8 Desktop mode). Telerik has been helping Windows developers for over 11 years, and is still very committed to developing .NET applications for Windows.
Windows Presentation Foundation (WPF) is the goto framework for building Windows applications. And with Telerik UI for WPF, your applications will shine. With the most complete suite of UI controls, MVVM support built in, touch support, a wide array of themes, plus much more, it’s a must have for your development toolbox. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/products/wpf/overview.aspx.
Silverlight is still supported by Microsoft, and there isn’t any reason to re-write your Silverlight apps when they still fit your needs. With Telerik UI for Silverlight, you can create engaging, interactive user experiences for the Web and Desktop. With over 65 controls, MVVM support, touch ready themes, and much more, your Silverlight development can be a breeze. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/products/silverlight/overview.aspx.
There are still many WinForms apps in production, and with Telerik UI for WinForms you can keep making those apps even better. With over 60 controls, touch support, productivity tools, and extreme performance, it’s easy to make your apps shine! To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/products/winforms.aspx.
Kendo UI Mobile
Mobile developers can leverage Telerik Kendo UI Mobile to create iOS, Android and Windows Phone hybrid apps that not only look amazing, but can also automatically adjust to follow the recommended UI guidelines for each platform. Providing a complete Mobile Application Framework, Kendo UI Mobile is ready for the app stores, provides optional automatic layout, and many more features. To see these and all of the additional features and to try them for yourself, click here: http://www.telerik.com/kendo-ui-mobile.
UI for PhoneGap
Regardless of the platform, Telerik is there to help you Develop Experiences. Mobile, Desktop, Web, Native, or Hybrid, we have UI tools that can help you make your apps come alive. Built by developers for developers. Give them a spin today. All with free, fully functional trials.
Try the Telerik Platform: https://platform.telerik.com/
Register to attend the keynote on the telerik platform: http://get.telerik.com/launch-keynote
Philip Japikse is an international speaker, a Microsoft MVP, ASPInsider, INETA Community Champion, MCSD, CSM/ CSP, and a passionate member of the developer community. Phil has been working with .Net since the first betas, developing software for over 20 years, and heavily involved in the agile community since 2005. Phil also hosts the Hallway Conversations podcast (www.hallwayconversations.com) and serves as the Lead Director for the Cincinnati .Net User’s Group (http://www.cinnug.org). You can follow Phil on twitter via www.twitter.com/skimedic, or read his personal blog at www.skimedic.com/blog.