Altabel Group's Blog

Archive for the ‘Apple’ Category

For years Microsoft has been the de facto desktop operating system. Now Apple is using its mobile devices to steal market and mindshare.

Pundits have long expected Apple to integrate its desktop and mobile operating systems; however, recent announcements at Apple’s Worldwide Developers Conference (WWDC) show that the company is doing far more than borrowing user interface elements. After some tentative starts, Apple has embarked on a full-scale integration between the company’s phone and desktop devices. With new releases of the software powering each, your laptop will soon be answering phone calls, and your phone will share text messages with your desktop, allowing you to fire off a missive from your MacBook to a colleague’s Android smartphone using standard text messaging. While not totally unexpected, the depth of integration is fairly impressive, and doubly so since I couldn’t help wondering during the announcements: why hadn’t Microsoft done this?

A constantly unfinished puzzle

By nearly any metric, Microsoft was years ahead of Apple in the smartphone and tablet space. While Apple was restructuring a fractured business and “playing” with handheld devices in the form of the Newton, Microsoft had produced several generations of its own PDA, and eventually a full-fledged smartphone that was feature rich, but failed to build a compelling user interface around its advanced feature set. Over half a decade before the iPhone launched, a lifetime in mobile technology, Microsoft was introducing tablets, only to be wiped off the face of the map by the iPad. Microsoft’s most obvious advantage in the mobile space was its dominance of the desktop.

If anyone built a mobile device that integrated tightly with the desktop, it should have been Microsoft.

Technology versus usability

While Microsoft may have missed a historic opportunity, more recently the company has been touting its merging of significant portions of its mobile and desktop code. Even user interface elements have begun to cross-pollinate, with the “modern” user interface that first appeared in Windows Phone featuring prominently on desktops and tablets. However, this technical integration is indicative of Microsoft’s larger problem.

As a company, Microsoft’s Achilles’ heel has been an inability to fully integrate different elements of its computing empire, and to present a user experience tailored to the task at hand, not pounded into a contrived, pre-existing Windows metaphor. From the Start button and stylus on a mobile phone, to its most recent technical integration of its environments that completely lacks in end-user benefit, Microsoft is missing the boat on developing a holistic computing experience. Frankly, I don’t care if my desktop and smartphone are running completely incompatible code from totally different vendors, as long as they’ll share information and work seamlessly together.

The Switzerland of computing?

While Microsoft may have missed this opportunity for its own devices, it still represents a key player in the overall computing landscape, and the long-predicted “demise of Windows” is likely several years away, if it occurs at all. An integrated experience between Microsoft smartphones and Windows desktops won’t meet with much excitement, primarily due to the limited market penetration of Windows phones. What would be interesting, however, is if Microsoft were to use its desktop dominance to integrate tightly with devices from Apple, Google, and others.

Such integration might seem far-fetched, but Microsoft already does this to an extent, with its Exchange server happily sharing mail, contacts, and calendars between everything from phones and tablets to laptops and web apps. Microsoft also has decades of experience integrating diverse hardware, and producing operating systems that run well on millions of combinations of hardware is no small feat. Just as Apple’s original iPod hit its stride when the company made it available for PCs, Microsoft could accelerate its cloud services and desktop OS, and ultimately make a compelling case for Windows Phone by providing tight integration with several mobile vendors.

In the mid and long terms, “winning” the mobility wars is not going to be about who sells the most devices, especially as computing transitions away from single devices and into a multi-platform, multi-device world. Microsoft has a chance to regain lost ground by tightly integrating its desktop and cloud services with today’s devices, allowing it to define tomorrow’s computing experience.

 

Kristina Kozlova

Kristina Kozlova
Kristina.Kozlova@altabel.com
Skype ID: kristinakozlova
Marketing Manager (LI page)
Altabel Group – Professional Software Development

There have been esimates that when Microsoft releases Office for the iPad, likely later this month, it could end up bringing in billions of additional dollars to Microsoft’s coffers. Is that hype and overkill, it will it really add that much to Microsoft’s bottom line?

It’s widely expected that on March 27, Microsoft CEO Satya Nadella will announce Office for the iPad. If that’s true, that will finally put an end to the “will-they-won’t-they” speculation that has swirled around the fate of the suite for years.

How much additional revenue will Microsoft bring in when it releases the suite? Morgan Stanley analyst Adam Holt says that Microsoft could get $2.5 billion in new Office revenue by releasing Office for the iPad. And Gerry Purdy, principal of MobileTrax, offers even bigger numbers. He believe that Microsoft could gain an additional $1.25 billion in revenue in the first year Microsoft releases Office for the iPad and Android tablets, and $6 billion in annual revenue by 2017.

I think both numbers are wildly inflated. Take a look at Purdy’s reasoning,which is based on Microsoft releasing Office for both Android and the iPad.

He assumes that 25% of iOS and Android tablet users would buy Office and that Microsoft would net $50 per copy sold. He believes that Microsoft will sell Office for the tablets as standalones, rather than include it as part of a subscription to Office 365.

Purdy is likely wrong on both counts. It’s hard to imagine a quarter of all iPad and tablet users buying Office, especially because there are so many free or very low-cost alternatives, including the free Google Docs and Google’s Quickoffice. I’m sure that the percentage of people willing to pay for Office is far, far under 25 percent.

In addition, it’s quite likely that Office will be sold as part of an Office 365 subscription, not as a standalone piece of software. Microsoft has made clear that subscription-based Office is the future, and standalone Office is the past. As just one piece of evidence, Microsoft recently announced a cheaper Office 365 subscription, called Office 365 Personal, that appears to be aimed at those with iPads. It will cost $6.99 a month, or $69.99 for a year for one PC or Mac and one tablet compared to $9.99 per month or $99.99 per year for five devices for the normal subscription version of Office. That means that only some part of additional Office revenue shoud be attributed to the iPad, not all of it.

But that doesn’t really matter. Releasing Office for the iPad is not only about additional revenue. It’s also being done to protect existing revenue and market share. Microsoft needs to fend off Google Docs, which is free and works on all platforms. Releasing Office for the iPad is an important way to do that.

That will be even more important in future years. Rumors are that a 12-inch iPad may eventually come down the pike. If true, that would put it at the screen size of a laptop, and make it more likely that iPad owners will want a productivity suite. If Microsoft wants to keep its hold on the office productivity market, Office needs to be available for the iPad, and at some point, Android tablets as well.

Lina Deveikyte

Lina Deveikyte
Lina.Deveikyte@altabel.com 
Skype ID: lina_deveikyte
Marketing Manager (LI page)
Altabel Group – Professional Software Development

After Apple slammed Microsoft for gouging customers and designing tablets that nobody wants, Microsoft has fired back, saying that you can’t get real work done with iPads or its anemic iWorks productivity suite, and that iPads are little more than toys. Who’s right in the increasingly nasty war of words?

At Apple’s iPad launch, CEO Tim Cook and others zinged Microsoft for charging $99 a year for Office, charging $199 for people to upgrade to Windows 8, and for having a confused tablet strategy. CEO Tim Cook said about Microsoft:

“They’re confused. They chased after netbooks. Now they’re trying to make PCs into tablets and tablets into PCs. Who knows what they’ll do next? I can’t answer that question, but I can tell you that we’re focused.”

Microsoft is striking back, and striking back hard, esssentially claiming that you can’t get serious work done on an iPad, and that the only reason Apple is now giving away its iWorks suite is that no one wants to buy it. On the Official Microsoft Blog, Frank Shaw, Corporate Vice President of Communications at Microsoft noted the criticisms that Apple had aimed at Microsoft, and shot back:

“Seems like the RDF (Reality Distortion Field) typically generated by an Apple event has extended beyond Cupertino.”

And then he took off the kid gloves, criticizing Apple’s new iPads as overpriced, iWork as a pointless piece of software, and saying they don’t stack up against Surface tablets when it comes to productivity. He wrote:

“Surface and Surface 2 both include Office, the world’s most popular, most powerful productivity software for free and are priced below both the iPad 2 and iPad Air respectively. Making Apple’s decision to build the price of their less popular and less powerful iWork into their tablets not a very big (or very good) deal.”

He said iPads were not suitable for getting real work done, and that the reason Apple is giving away iWork for free is that no one wants them, as shown by their $10 price for iOS, or $20 for Mac OS X. He wrote:

“…it’s not surprising that we see other folks now talking about how much ‘work’ you can get done on their devices. Adding watered down productivity apps. Bolting on aftermarket input devices. All in an effort to convince people that their entertainment devices are really work machines.

“In that spirit, Apple announced yesterday that they were dropping their fees on their ‘iWork’ suite of apps. Now, since iWork has never gotten much traction, and was already priced like an afterthought, it’s hardly that surprising or significant a move. And it doesn’t change the fact that it’s much harder to get work done on a device that lacks precision input and a desktop for true side-by-side multitasking.”

And he concluded that when it comes to getting real work done, Apple is far behind Microsoft:

“So, when I see Apple drop the price of their struggling, lightweight productivity apps, I don’t see a shot across our bow, I see an attempt to play catch up.”

Who’s right here? When it comes to the productivity argument, Microsoft is. There’s absolutely no doubt that a Surface Pro 2 tablet equipped with a Touch Type 2 keyboard and a free version of Office is a far more effective tool for getting serious work done than an iPad with iWork. In essence, the Surface Pro with the Touch Type 2 keyboard is an ultrabook. An iPad with iWork is…well, an iPad with iWork. In other words, fine for light work. Not well-suited for serious work.

But when it comes to the tablet market and to sales, Apple is right. For now, tablet buyers don’t care about doing heavy-duty work on them. Checking email, browsing the Web, running apps, and light memo writing, are all well-suited for tablets. And that’s all many people need to do for their work.

So in the tablet battle, Microsoft’s Surface may be on top for productivity. But when it comes to the bottom line and sales, Apple is still cleaning up.

Kristina Kozlova

Kristina Kozlova
Kristina.Kozlova@altabel.com
Skype ID: kristinakozlova
Marketing Manager (LI page)
Altabel Group – Professional Software Development

Responsive web design isn’t the future, it’s the present

In our humble opinion it’s late to debate whether responsive web design is the future because it’s already the present of everybody’s business represented online. Consumer/client behavior has been changing. According to statistics and analysts’ predictions, for instance, for the first time since 2001, PC sales are projected to be lower than they were in 2012; smartphone sales will double PC sales in 2014; tablet sales are expected to exceed 100 million this year and may top notebooks next year. So the shift to mobile is happening at an extraordinary speed, and tablets and smartphones are becoming extremely popular for business and pleasure matters. This means people view your content on thousands of oddly shaped and different sized screens. What’s more, according to Google research, mobile users “expect their mobile experience to be as good as their desktop experience” – this expectation poses a thorny challenge for both, business stakeholders and web designers and developers.

So this is no longer about “How do I make my website available to a smartphone or tablet?” – it’s “How do I make my business available in smartphone and tablet context?”. For some business it’s not important – it’s literally critical, for example: according to the Pew Research Center, 60% of tablet users prefer reading news on the mobile web than via an app; the same percentage is quite common for e-commerce sites according to Google Analytics and that’s why RWD has been listed in E-commerce marketing checklist for 2013. If you wish to identify the percentage of your audience that use mobile devices use the Google Analytics Mobile Overview report feature: if mobile users are more than 5% of your total audience you should consider catering for them too.

In general, there are three main approaches to providing information and interaction to mobile/tablet device users : responsive (and adaptive) web design, mobilized websites, and mobile apps. It’s important to understand that these are different marketing channels and their value proposition is very different. A mobile web site may do something very different from a mobile app – simply said, “if your goal is just to display and show content beautifully create a responsive or mobilized website; if your goal is to show productivity tools, build an app”. Which option is the best for your business will depend on your use case, your users’ habits and your budget.

Responsive web design vs mobile web development: advantages and challenges

To talk about advantages of responsive web design, let’s start from its definition. RWD is a front-end development approach aimed at crafting device agnostic sites. It uses “media queries” to figure out what resolution of device it’s being served on. Flexible images and fluid grids then size correctly to fit the screen. So responsive design provides easy reading and navigation with a minimum of resizing, panning, and scrolling, and eliminates the need for separate sites for different devices. Adaptive web design is either a subset of responsive design, or a related approach. “Responsive design will show more stuff or less, optimized for a mobile layout, but is likely to still provide access to the full desktop-view’s content. Adaptive design, by contrast, might show very different content, and also present a different UI, reflecting touchscreen’s tap/swipe/scroll versus desktop’s keyboard/mouse interaction.” In either case, responsive (and adaptive) web design will be based on the same code as a desktop site, and will locate on the same URL.

- In the definition above a couple of advantages of RWD are pointed out. Indeed, it improves user web browsing experience since a website adapts to the browser or device compatibility automatically and makes the content look good. For customers it shows that your business is receptive to changing technology and understanding of consumers’ needs.

- From business perspective, “one website – multiple devices” concept means that it’s easy to manage and focus on developing good content for your website. The same applies to analytics and strategy development and deployment since there is only one set of analytics to examine and a single strategy to develop and deploy. From maintenance standpoint, the technique is great too as one update affects all of your platforms.

- Additionally, responsive websites are easier for consumers to find than traditional or mobile web sites because they come up higher in search engines’ rankings. “In fact, Google recommends responsive web design because having a single URL for desktop and mobile sites makes it easier for Google to discover content and for Google’s algorithms to assign indexing properties to content.”

- One more advantage from the future perspective, as Resnick predicts, is: “As the internet transforms further into a platform of services and user interfaces that tie those services together, leveraging RWD technology in the future will allow companies to integrate a plethora of back-end services, such as Facebook, Twitter, Salesforce.com, and Amazon Web Services, and then present the integrated data back out the front-end iad layer on a responsive design so the application looks great on all devices without custom coding needed for each device or screen size. No longer are expensive back-end solutions needed to integrate legacy systems with business partners.”

Actually responsive web design is quite immature so it faces many challenges too.

- Even though we might view a responsive website on a smaller screen and it displays less visible content or smaller-sized images, this does not mean that the site will load faster. The thing is that from one side responsive websites are not much smaller in download size when viewed on smaller devices or screen resolutions compared to when being viewed on a desktop browser jacked into a broadband internet service provider, on the other hand mobile internet speeds still lag much behind broadband internet ones. Thus responsive web sites need advanced optimization, such as serving smaller images and conditionally loading scripts, and much more. An alternative may be found in dedicated mobile web development solutions since they specifically address mobile devices.

- The related issue concerns complexity. Responsive web designs are inherently complex because they are trying to support many viewing experiences without necessarily optimizing the experience for one particular device (or genre of devices). Mobile browsers will have to deal with a big HTML file, and the site would need to carefully avoid running specific scripts, loading certain CSS and download large images. Perfect implementation is possible, still avoiding over-resourcing requires scripts or code and therefore additional complexity. Typical “m dot” site wins in this case and is simple. It usually has a small amount of HTML, limited scripts, CSS, and images (if at all) as it is built specifically for its intended small-screen, touchscreen mobile devices viewing experience.

- As for UI and UX, responsive websites have limitations here. Not only in screen size, they are also limited for utilizing or recognizing key mobile features such as user location, connectivity, device limitations, software potential, and user needs. Mobilized sites and mobile apps will provide broader opportunities and advantages here.

- Information architecture can be an issue. It needs to be carefully considered and should be hierarchically structured before the design implementation.

- Advertising is an issue. Ads will have to shift with the sites, something that will wreak havoc with advertisers who want guaranteed placements on sites.

So, which approach will or do you use to present your business online?

HTML5’s momentum and Best tools for responsive web design

Responsive web design is not a specific technology but a whole design approach. However, responsive design is enabled primarily by CSS3 and JavaScript, which fall under the banner of HTML5. HTML5 is really maturing in terms of its functionality and, more importantly, its speed. So now HTML5 is the backbone of the new and interactive features of responsive web design.

To achieve a smooth flow from a large screen to a small one it takes a lot of patience and perseverance. To reach a seamless result there are a number of tools that help you with it. Below you will find a list of best responsive design tools broadly recommended in the web as well as by Altabel’s dev team:

1. Gridset
A tool that helps you design, prototype and build any type of grid layout required – columnar grids, asymmetrical, fixed, fluid or responsive grids. It even lets you create a library of your own grids, with a variety of presets available. It will allow you to build responsive prototypes (without all the calculations) very quickly and easily, providing all the measurements and tools to integrate with your existing markup.
Alternatives: Frameless, Tiny Fluid Grid, Gridpak, SimpleGrid, Responsify, Responsive.gs, Golden Grid System and Photoshop Grid for Responsive Design.

2. Bootstrap
An intuitive and powerful front-end framework from Twitter to start a responsive website fast and easy. It addresses the most popular user interface components and interactions, uses a 12-column responsive grid system with simple and flexible HTML, CSS, and Javascript and features dozens of components, styles and JavaScript plug-ins, with basic global display, typography and link styles all set. It also gives the option of customizing components of your website for instance by using the Customizer .
Alternatives: Skeleton, Foundation, Base, InuitCSS, LESS Framework, Gridless, 320 and Upand Gumby.

3. Wirefy
Clients wish to see how wireframes will adapt to different device sizes. Static wireframes aren’t particularly useful to show a client how responsive your design is, or what functionality is being suggested. But rapid prototyping by building flexible wireframes may. Wirefy is a collection of functional responsive HTML snippets and templates that scale as the browser is resized (working across multiple devices). It builds on tools such as the Frameless grid system and Bootstrap, and uses CSS media queries that adapt to different device resolutions. Wirefy focuses on key elements such as typography, tables, images, slideshow, forms, tab panel, paginator, menu, etc., focusing on the users.
Alternatives: Froont, Interactive Style Tiles, Responsive Sketch Sheets, Responsive Wireframe Template, Interface Sketch Templates, Responsive Device Diagrams, Wirify.

4. FlevNav
Navigation strategy is a really critical component of any responsive website design. FlexNav is a jQuery plugin that takes a device-agnostic approach to complex site navigation. It is a mobile-first concept using media queries and JavaScript to create a menu with drop downs. It features multiple nested sub-menus, with support for em units and tap targets to reveal sub-menus for touchscreens.
Alternatives: TinyNav.js, Navigation Patterns for Responsive Design, MeanMenu, Responsive Solutions for Menu Navigation, jPanelMenu.

5. Adaptive Images
Previously, making your website images responsive was tricky and usually meant using a “hack-around”. Now several tools may simplify this task. Using a one htaccess file, one php file and a single line of JavaScript, Adaptive Images detects screen size of browsing devices, cashes and delivers device appropriate re-scaled versions of your web page’s embedded HTML images without any mark-up changes. Also it is entirely non-destructive, and works on existing websites and markups — without the need to edit anything. Adaptive Images works on the premise that you are already using the highest-resolution images on your site, and also offers a ton of customization options.
Alternatives: ReSRC.it, jQuery Picture, ResponsiveImg, Retina.js and Retina Images.

6. FitText
As content scales according to a user’s viewport, the text will naturally wrap as the container is narrowed; and this often causes widows, orphans or your headlines to look rather ugly, and can even break the entire layout. FitText is a jQuery plugin specifically for headlines and big text. It auto-updates the font size according to the width of the element wrapping it, so you can achieve scalable headlines and a non-broken layout that can be caused by font-sizing issues. FitText works perfectly with Lettering.js or any CSS3 property thrown at it. There are options to fine-tune the text, including the ability to set min-max sizes and the level of scaling. Still FitText is only for headlines, and shouldn’t be used with paragraph text.
Alternatives: BigText, Lettering.js, Kerning.js, Kern.js, Type Butter and Slabtext.

7. Responsive Slides
This lightweight plugin allows you to create a responsive slider using elements inside a container. The images have to be the same size and jQuery 1.6 and up should be used. You can keep captions and other non-HTML elements inside the slides, while also using CSS3 transitions with JavaScript fallback. It works in all major desktop and mobile browsers, can support multiple slide shows, have settings for transition and timeout durations, automatic and manual fade, and have options for customization.
Alternatives: Flex Slider, Slides.js, PhotoSwipe, Supersized, Camera, RefineSlide, BlueberrySequence.js and Galleria.

8. Responsive Tables
Data tables in responsive design can be troublesome: you want it to not break responsive layouts, not hide content, let you see entire rows and columns, not be too small to read easily or zoomed in too far requiring scrolling. Here ZURB comes out – a simple JavaScript/CSS combination containing two key files: responsive-tables.js and responsive-tables.css. It works by taking the first column, which is often the unique key for a table, and “pinning” it to the left of the table, allowing you to scroll the other columns under it.
Alternatives: Responsive Data Tables, Stackable.js, Footable, Responsive Tables, Responsive Tables, Responsive SEO Friendly Data Tables.

9. Responsive Design Testing
Building a responsive website means constantly testing how it displays across mobile and tablet devices. You could resize the browser yourself, or use a browser extension or tools within your IDE; but there is an extremely simple tool that allows you to see how a page displays on different screen sizes, in a single view. With Matt Kersley’s RWD testing tool you just have to enter your website’s URL into the address bar to test a specific page in different widths and device sizes. Also you can share the results of the test with others by adding any URL to the end of the testing page address. One major benefit of this tool is that it can be self-hosted (available on GitHub) by downloading and installing it on your own site. You can then navigate through the frames that your website appears in, testing the entire site effortlessly.
Alternatives: Screen Queries, Screenfly, Responsivepx, Responsinator, Responsive ViewportResponsive.is, and Resize My Browser.

10. Respond.js
The problem with media queries in responsive web design is that they are a part of CSS3 specifications so they do not work with older browser versions such as IE8 and lower. Respond.js comes to the rescue for browsers that don’t support media queries directly, translating any media queries it finds into equivalent JavaScript.The script itself is incredibly small and lightweight. It works unobtrusively, and doesn’t rely on any other scripts or frameworks to run.
Alternatives: Modernizer, Adapt, Categorizr, CSS3 Media Queries and Enquire.js.

The tools above are ultra useful for any RWD project from the planning and designing phase right through to testing, and what’re your favorites?

Welcome to share your view points.

Helen Boyarchuk

Helen Boyarchuk
Helen.Boyarchuk@altabel.com
Skype ID: helen_boyarchuk
Business Development Manager (LI page)
Altabel Group – Professional Software Development

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

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.

Apps-like sites
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 :)

Aliona Kavalevich

Aliona Kavalevich
Aliona.Kavalevich@altabel.com
Skype ID: aliona_kavalevich
Business Development Manager (LI page)
Altabel Group – Professional Software Development


%d bloggers like this: