Posts Tagged ‘mobile’
WHAT TO CHOOSE TO MOBILIZE YOUR SITE: MOBIFY/BMOBILIZED, NATIVE APP, RESPONSIVE DESIGN OR MOBILE VERSION FROM THE MAIN SITE?
Posted April 18, 2013on:
WHY DO YOU NEED A MOBILE FRIENDLY WEBSITE
There is no secret to anyone that people are browsing the web more from their smartphones and tablets rather than from traditional computers. So having a mobile-friendly site for business nowadays is more important than ever. This is both a big problem and a big opportunity for businesses seeking to engage with new customers.
In the end of 2012, Google conducted an independent survey to learn what users want most from mobile sites today. And the numbers are striking! In fact mobile-friendly site can turn users into customers, according to a survey about 67 percent indicated they would be more likely to purchase a product or service from a business that built a mobile-friendly website. On the contrary not having a mobile-friendly site helps your competitors , for example, 61 percent of users indicated that they’d leave a site that’s not optimized for mobile. Actually non-mobile friendly sites can hurt a company’s reputation: about 52% of users said that a bad mobile experience made them less likely to engage with a company and 48% said that if a site didn’t work well on their smartphones, it made them feel like the company didn’t care about their business
HOW TO MAKE YOUR SITE MOBILE
Just shrinking your text into the device’s screen won’t give good impression about your business to the customer. The development of your mobile site should be determined by the kinds of products and services your business provides.
There are several options how to optimize your website for mobile, free and paid, having their own pros and cons. Here are a few strategies how to make your site mobile friendly:
- Mobile Website Conversion Service
There is a number of services on the web, that will convert your existing website and provide a script that will direct mobile users to your newly created mobile site from the main website. Among these services are Duda Mobile, bMobilized, and Mobify
- Separate Native Mobile Site
Some businesses want to keep their desktop and mobile websites separate. By creating a mobile website, you maintain control: its design, maintenance, hosting, and security. A script will be added to the main website that will determine if the visitor is using a mobile device and if so, it will automatically direct the visitor to the mobile version.
- Responsive Design
Responsive design is becoming more and more popular. It allows having one website that will display correctly on all devices — desktop, laptop, tablet, or smartphone. It takes advantage of CSS “media queries” to style pages based on the width of the device being used. To determine if your website is responsive, just resize the browser window. If it adjusts — so that the images and text are readable with a narrower browser window — it’s responsive.
-Mobile Version from the Main Site
Some e-commerce providers are heading for mobile. For example, Magento has taken its way to mobile commerce! Magento Mobile introduces exciting Free of cost Magento Mobile extension which allows store owners to manage multiple native applications across various mobile devices from a single Magento interface and provides support for iPhone, iPad and Android base mobile devices. The beauty of Magento Mobile is that it integrates just seamlessly with your account management, product catalog and checkout functions and facilitates your users to experience the same functionality of web store on their mobile devices.
In this article I wanted to draw your attention to the importance of optimizing your website to mobile. Is having a mobile friendly website important for you?
Anna Kozik – Business Development Manager (LI page)
Anna.Kozik@altabel.com |Skype kozik_anna
Altabel Group – Professional Software Development
Nowadays, more and more people use their mobile devices for the majority of their computer needs. That’s why mobile web application frameworks are in high demand for developers. There are several great mobile web frameworks that allow you to create an application with a native “look and feel” interface. Among them are jQuery Mobile, Sencha Touch, iWebKit, DHTMLX Touch, etc. If you have decided to develop a web application for mobile devices and you want to use a client-side framework to achieve this, Sencha Touch (ST) and JQueryMobile (JQM) seem to be the most serious options. What are their strong and weak points? Let’s see.
ST comes with a MVC framework which leads to a well structured code base. It is really a big plus, especially for large projects. Using ST you will likely not have to write a lot of HTML as the DOM (Document Object Model )is generated out of the objects models / widgets that you use. Besides, a wide range of UI widgets to choose from, as well as robust data, layout and component models are at your disposal.
Speaking of device support, ST website actually supports iPhone, Android and BlackBerry. It works really good on iOS. As for Android, it can be slow on large lists. Some problems may occur with Blackberry, so it may be better to choose another framework for this device.
ST also has enhanced support for touch events such as double tap, swipe, hold, pinch and rotate.
Developing on your desktop you should keep in mind that ST does not support all browser engines. You are required to use a browser based on Webkit (like Google Chrome or Safari). You are not able to view Sencha Touch apps in Firefox, Internet Explorer, or any other browser not using the Webkit engine.
ST is not easy to get running on the fly. It is almost a purely programmatic model, as you don’t design pages in HTML, but programmatically add elements to a page. So sometimes it’s difficult to make web design separately in HTML.
As for converting sites to work with the framework, it may involve a full front-end rewrite and it is very hard to debug and fix errors in ST.
Pros: MVC codebase; good support of iOS; enhanced support for touch events; great API documentation and sample demos
JQM is Touch-Optimized Web Framework for Smartphones & Tablets. It is a unified user interface system across all popular mobile device platforms, built on the rock-solid jQuery and jQuery UI foundation.
JQM is really quick to develop with. You can just start with clean HTML markup and then apply “progressive enhancement techniques” or extra HTML element attributes to integrate mobile features into an existing semantic structure.
As for MVC, JQM doesn’t have it. So lot of care has to be taken while organizing the code.
The framework claims to offer a broad level of support across a wide range of platforms, and progressive enhancement for older devices and operating systems. Instead of writing unique apps for each mobile device or OS, the jQuery mobile framework will allow you to design a single highly branded and customized web application that will work on all popular smartphone and tablet platforms.
JQM includes a great AJAX-powered navigation system which enables animated page transitions while maintaining back button, bookmarking and clean URLs.
The framework comes with a CSS theme styling system that enables a simple project to get off the ground very quickly. Then this can be easily extended with your own custom styles. But the CSS theme styling system has limited options so sites built can look similar.
The bad thing is that page transitions and animations don’t feel ‘native’ enough and can be sluggish sometimes.
Pros: JQM is quick to develop with; supports all major browsers and platforms; has a great AJAX-powered navigation system; CSS theme styling system enables a simple project start very quickly
Cons: no given code structure (MVC); CSS theme styling system has limited options (sites may look similar); page transitions and animations don’t feel ‘native’ enough
So after comparing these two frameworks on some points, we see that ST has a given code structure and feels more like coding in Java/C# while jQuery Mobile is more like web with the HTML you write. So it’s better to use ST if you are used to Java/C# and only want to support such devices as iPhone and Android. And if you are a webdeveloper, used to jQuery and HTML and want to support the majority of devices and browsers, using jQuery Mobile seems to be more sound.
And what are your thoughts? I’m eager to know which mobile web application framework will you define as the best solution for developing a web app for a mobile device? Will it be Sencha Touch or jQuery mobile or some other great framework? Thanks and looking forward to your comments!
With the growing popularity of smartphones, tablets and other mobile devices the living has become more comfortable. The different types of apps help us to wake up in time, to entertain reading books, booking tickets, listening to favorite music and just chat with friends without extra expenses. Among the challenges in mobile app market stands also the developing of effective web browsing solutions.
In this article I would like to take a look at DHTMLX Touch framework that helps to create nice-looking and easy-to-use mobile web apps oriented to touchscreen devices.
Let’s see what the characteristics of DHTMLX Touch are:
-compatible with the main web browsers for mobile platforms that support HTML5;
-free under both GNU GPL and commercial Licenses;
-lots of technical samples with the source code that simplify studying how the UI elements work;
- expanded builder tools:
• Skin Builder – an online tool that allows you to build mobile web apps through a user-friendly, drag-and-drop interface. Since v.1.2, you can save your design or share it by sending an URL.
• Visual Designer - a simple online tool that provides an easy way to choose the skin for you app and customize the skin colors. A set of predefined skins is included.
-server side is based on the on dhtmlxConnectors (the same that used for DHTMLX Ajax library) that simplifies client –server communication;
- simplified scheme of CSS editing.
The current version of DHTMLX Touch framework took a long way from the release of its first components dhtmlxTree and dhtmlxGrid in 2005-2006 to become a complete tool that covers the most required aspects of modern application interface. Three months ago in September, 2012 was presented the updated version 1.2. And now we will see what are the new features and improvements were added:
* Bug fixing – more stable and faster performance, better compatibility with the latest iOS and Android platforms;
* Updated visual designer tool: new Unitlist component, new charts, and the ability to share and save your design;
* Auto-complete for IDEs: Microsoft Visual Studio, PHPStorm, WebStorm, NetBeans, Aptana Studio, Eclipse, and others
* Multiple fixes in form validation logic
* Better memory management: automatic destructors clean up the memory, which helps to prevent memory leaks if the app has a complicated inheritance structure
* Better support of full-screen mode
Many companies around the world make the preference towards DHTMLX saying that it’s very simple, flexible and easy-to-use with a live support forum.
If you have already an experience working with DHTMLX Touch framework or heard something about using it, feel free to share your thoughts/experience by leaving a comment.
You can also have a look at new features of DHTMLX Touch framework and the samples of apps already implemented following the link to the official website http://dhtmlx.com.
Posted November 26, 2012on:
Nowadays, it goes without saying that mobile devices and apps are changing not only the way of users’ interaction with each other but also how enterprises interact with their processes, customers and employees. The important factor here is the platform that hosts the mobile apps. So enterprise faces the necessity to select the platform which will best suit goals that enterprise pursues, mobile strategy it is following and of course budget it has.
One of such solutions is Mobile Enterprise Application Platform (MEAP). As Wiki gives it: “MEAP is a comprehensive suite of products and services that enable development of mobile applications.” MEAP manages the diversity of devices, platforms, networks and users. It allows an enterprise to develop an application once and then deploy it to a variety of mobile devices. According to Gartner, using a common mobility platform, like a MEAP, brings considerable savings and strategic advantages in this situation.
But before choosing MEAP as a platform, organization should decide if it really needs it. So let’s see when MEAP is a right solution, what it gives to an enterprise and what are the benefits it has.
When is MEAP a right solution?
Gartner proposed The Rule of Three, according to which enterprises are encouraged to consider MEAP as a solution when they need:
• To support three or more mobile applications
• To support three or more mobile operating systems (OS)
• To integrate three or more back-end data sources
What does MEAP give?
• Complete integrated development environment.
• Support for design, develop, test, deploy and manage mobile apps.
• Run-time middleware server to handle back-end systems of the enterprises.
• Robust security capabilities.
• Local and remote data handling capability.
• Ability to integrate external devices like credit card readers, scanners, printers etc.
What are the benefits of MEAP?
• Faster app development and deployment –MEAPs enable companies to spend less time on adapting applications for specific devices.
• Multiple feature integration- MEAPs allow easier integration of mobile apps with the unique features and capabilities of mobile devices and peripherals like credit card readers, printers and barcode scanners.
• Management-MEAP interfaces with client middleware server and back-end infrastructure to provide high visibility and control via web-based console over the environment. This makes it easy for the businesses to centrally manage devices and apps, and install and update mobile software over the air.
• Security- MEAP enforces guards against unauthorized access and helps in data security, in the event of loss or theft of device. It also enables constant monitoring in the mobile environment by generating detailed reports on user usage, devices and apps. The reports can not only be used for surveillance but also to manage various issues in the environment.
• Off-line Connection- Mobile apps, as smart clients in a MEAP environment, can work independently of a central server connection, allowing users to continue to work off-line.
• Robust back-end connectivity- MEAP provides strong connectivity between back-end infrastructure and mobile devices through mobile middleware thereby ensuring smooth flow of data to specified device.
• Support for scalability and new technologies – MEAP provides a highly scalable infrastructure to support dynamic increase in devices, apps and users. Being an open, flexible architecture, the platform also enables easy integration with emerging technologies.
So definitely, MEAP is bringing considerable benefits to enterprise. It can be a good solution that can help an enterprise to adopt mobility in a secure and efficient way. If an enterprise wishes to develop custom applications or deploy multiple applications on many device platforms, a MEAP solution rally makes sense. And have you ever dealt with MEAP? What do you think of its advantages? I’m eager to know your opinion! Thanks for your attention
Blackberry, iOS, Android, Windows Phone… the number of existing mobile platforms exceeds all reasonable limits while the developers can hardly choke down their moaning hearing cheery management appeals about supporting another platform…
I think when another mental eclipse caused by progressing deadline occurs, every person who is connected with software development has this banal thought – why is it not possible to make one project that would magically deploy on all the platforms in the native predictable view basing on one source code? There are a few frameworks that make this dream real.
In fact they use 3 approaches: interfaces generation based on
- C-like languages
– mixing these two approaches above
In some cases device-dependent things are boxed up into one package (in this respect AppCelerator upsets greatly, although the developers swear that do their best to optimize the resultant applications), or at the compilation moment there is a painful choice of the specific platform and device the package should fit (MoSync impressed with endless checkbox list sorted by brands and phones models). Commitment to flexibility constrains available functionality and productivity just because every platform has its own standard set of controls and its own view on optimum UX. In short, everything is not as rosy as we would like it to be, but these projects develop, lofty Partners sections on their sites pepper with sounding names, so we will not throw back this idea determinately – in the end everything depends on project aims and frames.
Below are the results of the experiments, when for the project realization a tool needed to be chosen. The criteria were simple: single code base, cross-platform (iOS, Android was enough), a possibility of creating own GUI elements, connection with web-services.
http://www.madewithmarmalade.com/ – the main language is C++ (code is written in Visual Studio or Xcode). It was mentioned about a possibility of using insertions written in native languages for the target platform. You can write for iOS with Windows. It has its own devices simulator. There were heard some complaints for resources voracity and the size of binaries in the output. The licence costs 500 USD.
http://xamarin.com/monotouch and http://xamarin.com/monoforandroid – The creators of the free Sharp version have been leading a very interesting project – Mono. They suggest commercial versions of the libraries for development in C# for Windows Phone, Android and iOs. If needed, it is possible to resort to C++, objective-C and work with the ready libraries that are specific for both platforms. A module for each platform costs 400 USD. The development processes in MonoDevelop IDE.
Embarcadero RAD Studio (a modern reincarnation of Delphi and C++ builder). Although their specialization is not mobile development, they provide very promising tools for developing applications for iOS based devices basing on Fire Monkey. They also say about forthcoming support of Android and Blackberry devices. For a single developer the price is a way too expensive (more than 3500 USD). There is no version for mobile development only, and it’s not worth considering until there is no support of additional mobile OS. At the same time it makes sense to keep a look out which side it develops.
If you know some similar tools, it would be interesting to read about them and your experience of using them-both successful and not.