background preloader


Facebook Twitter

Add support for standard HTML5 Drag and Drop operations on Mobile Devices. Download source and demo - 12 KB The Problem The HTML5 specification includes support for drag and drop operations. This is supported by all modern desktop browsers, but not by mobile browsers running under Android and IOS. This is a problem because one of the main reasons to develop applications using HTML5 is the ability to run on all devices. I suspect mobile browsers don't support drag and drop for two reasons: Their screens are often too small for useful drag/drop operations. But many mobile devices have screens that are large enough. Therefore, in order to use drag and drop on mobile devices today, you have two options: Forget about the HTML5 drag and drop APIs and use a custom drag-drop library (your own, or one of several existing options); or Use a polyfill that translates touch events into HTML5 drag and drop events. We prefer the second approach because standards are important.

For example, several Wijmo controls use HTML5 drag and drop extensively: The Solution Hide Copy Code. GitHub - liriliri/eruda: Console for Mobile Browsers. Mobile JavaScript Apps: The Problem with the Mobile Web. Creating an amazing mobile experience has become the holy grail for JavaScript developers in recent years. This is somewhat frustrating for web developers. We never had our day in the in sun. Just as we finally started to feel cozy around desktop browsers, the smartphone market exploded. We now faced slew of of new mobile browsers we had to deal with. These mobile browsers had far less processing power than their desktop counterparts. And they added new things we had to deal with like “gestures” and “touch events.” But life goes on. We switched from cursing at IE8 to cursing at the Android Stock Browser. We now mumble silently whenever someone mentions ServiceWorkers.

Safari has become the new Internet Explorer. But the mobile web isn’t enough. We want to bask in the App Store glory. We thought it would be easy. “Just stick a browser in there” we said. We were wrong. The Problem with Mobile Web Apps As engineers, we know that before solving a problem we must first understand it thoroughly. 1. Native or Not? The Untapped Power of Web Apps. This post was adapted from a talk I've been giving this year (BD Conf and Forge were awesome and you should register next year!). If you're interested in the slides, you can find them here: When I started as a Front-End Dev at Viget four years ago, building for "mobile" was still sort of a novelty. Today, everything we build is responsive, but it's been a slow journey figuring out how to translate the "wow" factor we have on desktop down to the tiny touchscreens in our hands.

While researching for a previous talk on mobile-first design, I found it incredibly hard to find exemplary, mold-breaking, mobile web experiences. Many "award-winning" sites featured on places like the FWA or either had no mobile experience at all, or displayed a dumbed-down version that lacked whatever it was that made the desktop experience stand out. Why is there such a disparity between native and web apps? Meanwhile, all the native apps coming were beautiful. See? Audio 1. Pourquoi les services publics anglais ont-ils décidé de bannir les applications mobiles ? Un ancien responsable explique. Dans une interview accordée à Govinsider, une publication spécialisée dans les services numériques du secteur public et gouvernemental, Ben Terrett, ancien patron du Governement Digital Service (GDS) britannique, qui est en charge de la transformation numérique des différents services publics, s’est expliqué au sujet des rapports entre son ancien service et les applications. « Nous avons banni les applications au GDS.

J’ai dit non », a-t-il avancé. La raison ? Les applications « coûtent cher en production et elles coûtent cher en maintenance parce que vous devez les mettre à jour lorsque surviennent des changements logiciels. Je dirais que si vous les multipliez par 300, vous vous retrouverez tout d’un coup avec une grosse équipe et un apport pécuniaire important pour maintenir cet écosystème ». Une évidence direz-vous ? Parmi les points de réflexion du GDS, le service a jugé bon de retirer toutes les questions et étapes qui n’étaient pas nécessaires dans un processus. - Silly-fast mobile prototyping.

React Native Review - The Transformation of Mobile Apps. The social media giant, Facebook is responsible for building the React.js JavaScript library for their engineering teams to create various interfaces for different operating systems using the same code. Facebook has once again surprised us by open sourcing what everyone has been waiting for; the React Native. First things first, React Native is not a direct competitor to frameworks like Ionic, Onsen UI, Kendo UI, jQuery Mobile.

Those frameworks are used to create hybrid mobile applications. At the same time, they require additional wrapper frameworks like Cordova or PhoneGap where they’re displayed inside a mobile platform webview. On the other hand, the final result of React Native is a real native mobile application. So it should be compared to frameworks like Titanium or Xamarin. Note: If this tutorial was helpful, need further clarification, something is not working or do you have a request for another Ionic post?

War between Hybrid and Native What is React Native Important Reminder. Review: 7 excellent mobile app builders. Over the last six months, I’ve been examining and testing a variety of mobile app builders and mobile back ends. In some cases, the app builders and back ends were part of a single product. In other cases, the app builders or back ends stood on their own. In this roundup, I’ll summarize seven products that are at least partially a mobile app builder.

Some have IDEs that run locally on your computer; others give you a Web IDE that lives in the cloud. Some are aimed at enterprise development, others at individual developers or even students. As we’ll see, they can have almost any level of complexity for the developer, ranging from drag-and-drop simple like EachScape, NSB/AppStudio, and Salesforce1, to providing an API for the developer to code against in Xcode or Eclipse, which is the way Appcelerator supports native SDK developers. They may be tied to an MBaaS (mobile back end as a service) platform or not. Alpha Anywhere The Alpha Anywhere IDE runs on Windows. AnyPresence. The Top 5 AngularJS Hybrid Mobile App Frameworks (Pros/Cons) It’s never late to learn something new especially if you’re full of ideas; you also don’t even need any prior native development knowledge. I’m writing this article for AngularJS community in a hope some of you will choose hybrid mobile application development.

You also don’t need to worry too much, hybrid mobile application development is not what it used to be. Long past are the days when everything hybrid was clunky and jerky, those frameworks are not with us anymore, new kids are here to step in their place. At the same time, you should also not live in the illusion, hybrid mobile application development is still not on the level of native development though this gap is getting shorter with every day. Intro Some time ago, I used to work a lot with jQuery Mobile. Table Of Contents Before we start take a look at a list of my chosen 7 in alphabetical order: Page 1 | Ionic FrameworkPage 1 | Kendo UIPage 1 | Mobile Angular UIPage 1 | Onsen UIPage 2 | SupersonicPage 2 | Conclusion Good Bad.