Posts Tagged ‘iOS’
There has been a lot of talk about the dirge sounding for the Firefox browser. With a marked nosedive in market share (roughly 15%), the one-time king of the browse war has now fallen into third place (behind Internet Explorer and Chrome). As most pundits are scratching their heads, I’m fairly certain that there’s a clear reason for this change:
The 15% market share applies only to desktop browsers. Once you move to mobile… all bets are off. But why? What has shifted to cause Firefox to drop so sharply? Is it a bad product? Honestly, to the majority of users (I’m talking “average user” here), a browser is a browser is a browser. The biggest difference to the average user is the use of “Favorites” over “Bookmarks.” Since most users wouldn’t even know Firefox from Internet Explorer, how could this change have happened?
Again, I say… Google.
Actually, I should be more specific and say Chrome — or even better, Chrome OS and Android.
From November 2013 to the end of the year, a reported 21% of all laptops sold were Chromebooks. Worldwide, Android takes nearly 81% of the mobile market share. That’s a LOT of Google-based browsers out there. I don’t think it’s a huge leap of logic to assume a vast percentage of those users would have been, otherwise, using Firefox.
Let me present myself a case in point. For the longest time, I was a devout Firefox user. But then I discovered a few of the Chrome apps/extensions (such as Tweetdeck) and added Chrome to my Linux desktop. Then I adopted a Chromebook as a laptop. Since I really only do two things on a laptop (write and browse), it made perfect sense. Add to this the fact that my smartphone platform has been Android for what seems like forever, plus the mobile version of Firefox is dreadful, and you have the makings for a typical migration from Firefox to Chrome.
Let’s be honest — as long as the browser gets the job done, it doesn’t matter which browser you use.
- Unless you’re on a Chromebook
- Or on Android
- Or you depend on Google Apps
You can see the pattern here, right? It’s like third-party politics in the United States. Many people don’t vote for third parties because it takes away votes from the party they once championed. In this case — every person using Chrome is one less person using Firefox. Why?
Caution: generalization coming…
Most people who use Internet Explorer simply don’t know that the product they’re using is inferior to every other product of its kind (either that or they depend on a site that was written ONLY for IE). So, there’s little to no chance they’ll jump ship to either Firefox or Chrome.
So, what is Mozilla to do? Well, they’re busy focusing on the Firefox OS, which is akin to Ubuntu focusing on the Ubuntu Phone — it’s detracting from what they’ve always done really well in exchange for jumping into a ring with two of the heaviest hitters in the history of the game — Android and iOS.
And then there’s that advertising deal with Google that’s about to expire. The majority of Mozilla’s income is from that deal, and Google has less reason to continue on with that search agreement. Google no longer needs the advertising real estate from a browser suffering from a possible slow death. Should Google pull this, Mozilla will have to pull off a miracle to stay in the fight.
However, there’s good news. You can’t forget that Firefox is an open-source browser. That means, even if Firefox were to die, another batch of forks would appear. So, even if Google Chrome were to knock Firefox out of the ring, more contenders will appear to take up the gloves. But even a horde of forks are not likely to pull Firefox from the slow Chrome burn. Google isn’t going anywhere but up. As Chromebooks and Android continue to take over the mobile planet (and users become less tethered to their desks), Firefox will continue to suffer.
Firefox is still a quality product. But like Internet Explorer, it’s facing a foe that’s stronger, faster, and more agile. That new opponent is poised to take over nearly everything it touches. Fortunately (for users, not the competition), that new foe offers a stellar product on every platform (Linux, Windows, Mac, Chrome OS, Android, and iOS). Chrome is the only browser on the planet that can make that claim (as Chrome is the only browser that will run on Chrome OS) – a claim that’s becoming ever more important in a world gone mad for mobile.
I don’t have a prediction for Firefox. Will it die? Will it become an “arm” of Google? Will it get a second wind and, thus, a second life? No one really knows at this point. If I had to make a guess, I’d say both Firefox and IE will fall to Chrome. The difference is that IE is embedded into the psyche of many users, so it won’t suffer as much as Firefox.
The gloves are off and Chrome is set to rumble. How do you think this fight will end? Share your opinion in the discussion thread below.
There exist a lot of mobile app development frameworks. Cross-platform tools reduce barriers to entry and democratise app development, by allowing developers from any language (HTML, Java, C++), any background (hobbyist, pros, agencies, corporates) and any skill level (visual designer to hard-core developer) to build mobile apps. Just imagine that by using a cross-platform tool and covering just two platforms such as Android and iOS, you will cover 91% of the whole smartphone market. Sounds appealing:)
PhoneGap and Sencha are the most widespread: they are used by 32% and 30% of cross-platform developers, irrespective of their primary tools. I`m suggesting to have a closer look at PhoneGap which turns to be the most popular tool.
How it works
-The most obvious one is cross-platform capabilities. Currently PhoneGap supports the following platforms: iOS, Android, webOS, Windows Phone, BlackBerry, Symbian OS, Tizen.
-Adjustments can be performed via browser; remote adjustments can be performed on a mobile device via “weinre”.
A blot on the landscape:)
- Users feel uncomfortable when touching a button and it doesn`t work. This is one of the most widespread bugs in PhoneGap apps. This bug appears due to improperly created interface, and it raises the problem of touching. The fact is that we look at the touchscreen at an angle and the visual contact area between the finger and the screen differs from the real contact area. This can be corrected quite simply – proper layout of the app page. For example, the area of response can be made bigger than the button itself.
-Nevertheless this is a cross-platform tool, UI should be optimized for different platforms. But it’s much faster, than creating another native app from scratch;
As you can see, these drawbacks are not quite ‘drawbacks’ in their nature, but rather technical conditions of PhoneGap, which you should consider, like in a usual development process for any other platform.
Certainly, PhoneGap is not a “miracle cure” but can be a good way out if wisely used. And what are your thoughts on PhoneGap?
iOS7 has been the greatest change to Apple`s iOS almost since its introduction. And iOS 7 differs quite a lot from its previous version. It`s easier, brighter, bolder and flows better than its predecessors. It has not only the updated user interface but also it`s packed with a great deal of new features.Let`s take a look at iOS7 and compare its major changes to iOS6.
Lock screen: One of the nicest features of iOS 7 is parallax effect: when you move the phone, wallpaper appears to move as well. iOS 7 gets rid of the black bars and becomes lighter. At first this may seem unusual but you get used to it quickly and won`t move back to the old look and feel. Also iOS 7 has four swipeable bits: unlocking, Camera, swiping down from the top of the screen to see notifications, and swiping up from the bottom to bring up Control Center.
Control Center: iOS users have been waiting for it for agesJ now there is no need to jump through endless Settings screen. Control Center is the answer: it provides quick access to the most important key features: Wi-Fi, Bluetooth, Airplane Mode, Rotation Lock and Do Not Disturb. It also provides media playback controls, Airdrop file sharing, and quick access to the phone’s LED light and the Clock, Calculator and Camera apps.
Notification Center: Last year iOS 6 introduced the Notification Centre – offering little gobbets of information from your email, or stocks, or Twitter, or games. It was pretty basic. Now it’s split into three elements – Today (a calendar and weather update), All (the things you used to find in the old Notifications) and Missed (appointments, calls). The calendar element is like Windows Phone, though more useful (you get a day view). You can decide what is visible in the lock screen – it won’t show all your notifications if you don’t want.
AirDrop: Thanks to AirDrop it became easier to share files from iOS devices. Now a “sharing” icon in an app lets you send your data to those willing to receive it. You choose AirDrop and you get a list of people in the vicinity. Press their icon, and it’s done. Nice, isn`t it?
If you don’t plan to use this feature in iOS 7 then turn it off to safe battery life.
Camera and Photos : Have also experienced great changes. Camera app now four kinds of shooting: video, photo, square (for Instagram-style shots) and Pano (for panoramas) and a number of pleasant new features.. As for Photos app, it`s became easier to search for photos as they are organized into collections. Your photos can be sorted by date or by location (when using GPS)
Safari/Search: It has also been updated: interface became simpler : it disappears completely when scrolling through pages, and the interface for switching tabs became more visual.
Mail: Mail application got some great new features: mail management became easier. There appeared gesture control for messages and smart mailboxes
Multitasking: Now you can double-click the home button in iOS to get you to a number of recently used apps. What is more iOS 7 learns when you like to use your apps and can update your content before you launch them. So if you tend to check your favorite social app at 9:00 every morning, your feed will be ready and waiting for you.
That was an overview of the main updates that experienced iOS7. Many things have changed and many users that updated to iOS 7 say that they will never return to iOS 6 :)
And what about you: have you already updated to iOS 7 and can share your experience?
Interesting to know your thoughts.
The Web as we know it have been born and matured on computers, but as it turns out now, computers no longer have dominance in it. According to a recent report by analyst Mary Meeker, mobile devices running iOS and Android now account for 45 percent of browsing, compared to just 35 percent for Windows machines. Moreover, Android and iOS have essentially achieved their share in just five years and their share is getting tremendously larger.
According to some forecasts their worldwide number of mobile devices users should overtake the worldwide number of PC users next year. If forecasts come true, this shift will not only continue, but accelerate. Based on data from Morgan Stanley, Meeker estimates roughly 2.9 billion people around the world will be using smartphones and tablets by 2015.
What does it mean now that more people are accessing the Web through tablets and smartphones rather than laptops and desktops? And is it really a big deal? Anyway, Internet is intended to be accessed from anywhere and thus from any device. Well, it is quite a change at least in terms most people consider the Web and how it gradually adapts to be used on mobile devices.
As mobile devices take over, the use of today’s desktop browsers like Internet Explorer, Chrome, Firefox, and Safari will decline. Mobile browsers are already very capable and will increasingly adopt HTML5 and leading-edge Web technologies. As mobile devices naturally have less screen area, the sites need to function more like mobile apps and less like collections of links. So the sites are likely to look like apps.
Apps may rule
Native apps for smartphones and tablets almost always surpass websites designed for mobile devices because they can tap into devices’ native capabilities for a more responsive and seamless experience. This is most likely to change in the nearest future – most experts agree HTML5 is eventually the way of the future. This is already the status quo in social gaming: for example Angry Birds and Words with Friends. Some services won’t be available at all to traditional PCs — they won’t be worth developers’ time.
Less information at once
Web sites and publishers will no longer be able to display everything new for users and hoping something will catch the user’s eye. Smaller screens and lower information density means sites will need to adjust to user preferences and profiles to customize the information they present. Increasingly, the Internet will become unusable unless sites believe they know who you are. Some services will handle these tasks themselves, but the most likely contenders for supplying digital identity credentials are Facebook, Google, Amazon, Apple, Twitter, and mobile carriers.
Sharing by default
In a mobile-focused Internet, anonymity becomes rare. Virtually every mobile device can be definitively associated with a single person (or small group of people). Defaults to share information and experiences with social circles and followers will be increasingly common, along with increasing reliance on disclosure of personal information (like location, status, and activities, and social connections) to drive key functionality. As the Internet re-orients around mobile, opting out of sharing will increasingly mean opting out of the Internet.
Emphasis on destination
Internet-based sites and services will increasingly function as a combination of content and functionality reluctant to link out to other sites or drive traffic (and potential advertising revenue) elsewhere. These have long been factors in many sites’ designs but mobile devices amplify these considerations by making traditional Web navigation awkward and difficult. Still URLs are not going to die – people will still send links to their friends and Web search will remain most users primary means of finding information online.
Going light weight
As people rely on mobile, cloud, and broadband services, the necessity to do things like commute, store large volumes of records or media, or patronize physical businesses will decline. Businesses won’t need to save years of invoices, statements, and paperwork in file boxes and storage facilities – cloud storage comes as their rescue. Banks will become purely virtual institutions consumers deal with online via their phones. Distance learning and collaborative tools will let students take their coursework with them anywhere — and eliminate the need to worry about reselling enormous textbooks.
Going mobile is an obvious trend today. Experts envisage that nearly every service, business, and person who wants to use the Internet will be thinking mobile first and PC second, if they think about PCs at all. Do you agree? And what other related changes can you imagine?
Many thanks for sharing your thoughts :)
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.
Thank you 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.
This time as a part of cross platform development I’d like to make a short review of Mono project’s implementations/frameworks – MonoTouch and Monodroidthat allow creating applications using .NET framework and languages.
MonoTouch is a framework that allows developers create iPhone applications using the compilation of C# and reusing the existing .NET source code, libraries and skills.
The MonoTouch includes:
• Mono for the iPhone, iPad and iPod Touch
• C# and .NET compilers – on the iPhone you will need to compile the existing C# code and tools with the help of MonoTouch compiler to make sure that all the assemblies are referenced.
• .NET Bindings to Native APIs – MonoTouch compiler turns to compile the .NET libraries and base assemblies to create native iPhone applications.
• Mac oriPhoneSDK -includes the Xcode IDE, iPhone Simulator, and a suite of additional tools for developing applications for iPhone, iPad and iPod Touch.
• MonoDevelop Integrationhelps developers to integrate all features/toolsets from the integrating.NET platform to the target iPhoneenvironment from zero in no time
• Libraries that bind the native CocoaTouch APIs – toolsets that help to create native application interfaces for iPhone, iPad and iPod Touch
Mono for Android (MonoDroid)is a software development environment kit that allows to create the applications that run on Android phones and tablets.
Mono for Android consists of the core Mono runtime, the Mono for Android bindings to the native Android APIs, a Visual Studio 2010 plug-in to develop Android applications and an SDK that contains the tools to build, debug and deploy your applications. The Visual Studio 2010 plug-in allows developers to use Visual Studio 2010 to develop, debug and deploy their applications to an Android simulator, an Android device, or the Android Application Store.
Being the customer of Mono product you get one-year subscription to its product updates. The updates engaged the bug fixes and API changes. You could check the latest updates for Mono on the website called Xamarian Developer Center following this linkhttp://docs.xamarin.com/.
One of the latest upgrades released in May of 2012 by Xamarian Mono for Android is considered the research project called XobotOS.
XobotOS – the attempt to put C# code in the place of removed Java code in Android operating system. The idea is to write native code using C# instead of Java seems to extend the opportunities of Mono project. As the developers say the transition from Dalvik to Mono virtual machine performed good results like high-performance and low-battery consuming. Sharpen was chosen as the tool convertor for porting million lines of Java code to C#. It was upgraded for XobotOs and presented as its part release. The next goal of the company isto provide the direct access to the graphics library Skia for building applications.
What is the pricing?
Monotouch/MonoDroidare available in Professional Edition and Enterprise Editions: Monotouch/MonoDroid costs $399 for the entry level Professional edition and $999 and $2,499 for the Enterprise and Enterprise Priority version. A trial version is available which isn’t time limited but only allows deployment to an iPhone simulator.
The development of applications using cross platforms development approach seems to give the right idea for the developers how to manage with different environments and languages. Having reviewed the Mono project frameworks the advantages both of them may be summed up as follows:
– Applications written in C# for Android (MonoDroid) could be easily ported to iOS (MonoTouch);
-The source code written on C#, could be reused in MonoDroid and MonoTouch;
– The full support of C#: Language Integrated Query (LINQ), delegates, lambdas, events, garbage collection and many other features
– The support of Visual Studio and XCodefor bothMonoDroid and MonoTouch
– New challenges and updates guides
If you know something about programming with MonoTouch/ModoDroid and you have anything to add to my review, please, feel free to share your thoughts and experience on this point.