Altabel Group's Blog

Posts Tagged ‘Google

When planning the application you have to choose the right programming language to make your application work appropriate. The choice depends on many factors you need to consider. Such as but not limited: you need to think over on what platform the application will run, how easily new features would be added to the existing platform, the code size, performance, support and community etc.

There are various web programming languages and selecting the right one makes a website function properly. In my article I would like to focus on three of them, so called three “P”: PHP, Perl and Python to answer which of these languages is the best one.

Let’s have a look at them and try to make a comparison analysis

PHP – is free of charge open source scripting language and widely used in web environment. The best advantage of PHP is that it is easy to learn and easy to use. It is flexible and used for developing from small websites to giant business and organizational websites. Most common are informative forums, chatting platforms, CRM solutions, e-commerce shopping carts, community websites, e-business, shopping carts.

In terms of efficiency it is executed by the server and server parses the code at its source, executes and send properly formatted html to the client computer. Therefore it increases the speed of PHP applications.
What concerns the advantage of running, PHP is multiplatform language and compatible with all operating systems and platforms.

Being open source language, a large group of PHP developers help in creating a support community, so it’s maintained and when bugs are found, it can be quickly fixed.
A lot of websites including such giants as Wikipedia, Yahoo!, Facebiook, Digg, WordPress and Youtube are written in PHP. The popularity of PHP is based on its simplicity and coding style that is quiet easy to understand.

Nevertheless, the simplicity in developing, precisely principle so called «structure is not important» in PHP has its reverse side, precisely it’s hard to maintain for large applications since it is not very modular.

Also it’s weak in terms of security since its open source, all people can see the source code, and if there are any bugs it could be used to explore the weakness. About 30% of all vulnerabilities listed on the National Vulnerability Database are linked to PHP. The last summary on vulnerabilities you may find following the link: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0427

Perl –refer to all purpose languages. Perl was developed as a text editor for converting or processing large amounts of data for tasks such as creating reports. Nowadays it intended improvements and suited for web development, game programming, GUI development, popular among system administrators etc.
The Perl reusable code structure provides flexibility in apps development and at the same time creates the problem of code reading after. As there are so many ways to do, there are a lot more ways to mess up in what you’ve done. If the code was written without proper care, the reading could even take 6 months.

So from one hand Perl is a good language for small programs because of its messy syntax structure it’s hard to write and maintain large programs. On the other hand if you’re planning to develop big web application you need to consider good coordination between developers work on discussing the code stile, mentoring and managing work in the team.

In terms of portability Perl code doesn’t use system specific features, so can be run on any platform.
Among popular websites created on Perl could be named bbc.co.uk, Amazon.com, LiveJournal.

In respect of vulnerability Perl takes the second place – 9.4%. I assume that it’s not bad taking into consideration its complexity and its long history.

It has fallen out of popularity lately a bit because of the slow development of Perl 6. Most people still use Perl 5.

Python – is considered to be very elegant programming language. It’s general purpose, high level programming language. On the one hand Python’s syntax and semantics are minimal; on the other it has complex standard libraries.

Python supports multiple paradigms: object-oriented, imperative and functional programming styles and has features including fully dynamic type system and automatic memory management.

In comparison with Perl Python is easy to read language. And its key idea is vice versa “there should be one—and preferably only one—obvious way to do it”. It means that the code written by one developer could be easily developed and supported by the others. Besides to delimit blocks Python uses whitespace indentation, rather than curly braces (C, C++, ….) or keywords (Delphi).

Python is often used as a scripting language, but is also used in 3D animation (Maya, Softimage XSI, Blender) and image editors (GIMP, Inkscape, Scribus, Paint Shop Pro). It was also used for writing several video games.

Python is actively used by Google, Yahoo!, CERN and NASA. But it has problems with popularity, precisely with spreading. The reason is that it’s less simple than PHP. Working with Python you need to learn numerical libraries. So that’s why some people prefer choosing PHP instead of Python. But only the betrayed ones could explain why they choose Python, the answer is easy the development on Python is faster on 30% and his vulnerability consists only 0.67% against 36% of PHP.

Conclusion

PHP at first sight seems to be a leader in this so called comparison race. It’s simple, easy to learn and efficient for building small and middle size websites. Going further with analysis in terms of scalable large system it turns out that here Python will perform better than PHP. The reason is in readability that makes Python easier to maintain and extend. Besides, Python is object-oriented. PHP is not. Moreover, Google supports Python with its Google App Engine where web sites can be hosted on Google’s server for free. What concerns Perl, analysis showed that it’s simple programming language with cross platform running and open source modular architecture that provides to develop interesting things. If the task is to perform administration scripts Perl is much better to use here than PHP.

After the analysis it follows that the choice any of three P is a good choice. Also it means that for a certain purpose there is a right tool to choose. Besides the analysis showed that all three “P” have in common the following:

• are cross platform;
• have open source code;
• have well written documentation;
• have large user communities;
• extend libraries and big amount of code written;
• have high-level frameworks (PHP – Symfony, php.MVC; Python-Django, CherryPy, Pylons; Perl -Catalyst, CGI::Application, Gantry);

So I hope that summary based on technical analysis we made could help to make a right decision in future web projects you might have.

Thank you for your attention and if you have anything to add, please feel free to leave a comment.

Kind regards,
Katerina Bulavskaya – Business Development Manager (LI page)
Katerina.Bulavskaya@altabel.com
Altabel Group – Professional Software Development

Debates about which programming language is the best are always hard and heated. Likewise, there’s no ideal language that works for all web application project requirements. Wikipedia is written in PHP. Gmail is written in Java. Python is number one choice of Google and YouTube. Ruby is used to create Twitter and Hulu. Slashdot is written in Perl. Stackoverflow is written in C#.

Browsing for the best web programming languages, among dynamic ones, you’ll mostly see PHP, Python and Ruby listed. Back in the days several years ago PHP was admitted the best tool for web job but since then both Python and Ruby have matured and grown robust libraries and frameworks around them that make them better candidates for many web projects now.

Today many consider PHP to be great for average everyday web systems. Python and Ruby are thought to be more suitable than PHP for most web applications in general and for more advanced things in particular. Just like PHP, they are free, open source, run on an open source stack (Apache and Nginx / linux, windows and BSD), and play well with any database engine. However, Ruby and Python have better syntax and they both enforce good programming habits by their nature, especially Python. PHP encourages sloppy spaghetti code by its nature. Also, the object oriented features in PHP are very ugly because of its arcane, retarded syntax.

Let’s get deeper insights into these two web programming languages from various standpoints:

As mentioned before, Python and Ruby are two of the most popular dynamic programming languages used in high level application development. In fact, Ruby was built using some of the design elements from Python. Developers often prototype using these two languages before implementing on compiled languages because of their modularity and object oriented features. Many use Python or Ruby instead of Perl as simple scripting languages. Python and Ruby are popular among web developers as well because of their rapid development cycle, with Python boasting computation efficiencies and Ruby boasting code design.

a/ Philosophy
Python really believes that code readability is the most important thing. Hence, there is one-true way of writing code, or as it has been reformulated lately: “There’s a most understandable way to do something and that is how it should be done”. Python is designed to strongly emphasize programmer productivity and it likes things to be structured, consistent, and simple. Python syntax enforces strict indentation rules; in fact, indentation has semantic meaning in Python.
Ruby believes in giving programmer the flexibility, freedom and power. It was designed, first and foremost, to make programming fun for its creator, with guiding concepts as follow: “The Principle of Least Surprise” and “There’s more than one way to do the same thing”. The latter philosophy principle inherited from Perl is the reason why many Ruby methods have alternate names, which may lead to some API confusion among new practitioners. However, this flexibility enables Ruby to be used as a meta language for describing DSL. Also Ruby provides a better way to write concise and compact code. More into the expressiveness of the code and writing code that is clever.
Python people like libraries to be transparent and obvious how they work and hence is easier to learn, while Ruby people tend to provide clean and pretty interfaces with “magic” behind the scenes. This makes development very fast when you understand the magic, but frustrating when you don’t.

b/ Ease of Use
Python is known for its ease of use. It allows beginners to start building powerful sites more quickly, and has the power to grow in complexity keeping its ease of comprehension. For example, one of the hardest parts of coding is going back to what you coded long ago and trying to remember the logic of it. Because Python uses natural language with white spaces and indenting, it is much more clear and easier to read than languages like Ruby. That makes it easier to fix mistakes or do updates. Also, there are literally thousands of pre-built modules that can be snapped on to let you get up and running on the web immediately. Its intuitive introduction to object-oriented coding concepts, such as communities, modules, and libraries, allows you to move on to other related programming languages as they develop.

c/ Object Oriented Programming
Both Python and Ruby support object oriented programming. Still Ruby’s object orientation is considered to be more ‘pure’ in that all functions exist inside a class of some sort. Python’s object orientation is more akin to that of C++, which allows functions and statements that exist outside of classes. In Ruby, even global variables are actually embedded within the ObjectSpace object. Python doesn’t have global variables, instead using attributes of module objects. In Python and Ruby, an instance of literally any type is an object. However, where in Ruby all functions and most operators are in fact methods of an object, in Python functions are first-class objects themselves.

d/ Syntax
Ruby includes several syntactic features which make dynamic extension of and higher-order interaction with external (library) code more straightforward. In particular these are blocks and mix-ins. Most things implementable with block and mix-in syntax are also achievable in Python, they are simply less syntactically natural and clear, and so less commonly form the centerpiece of major libraries or common styles of programming. These features, combined with a lighter-weight syntax with fewer restrictions (whitespace flexibility, optional parentheses, etc), make Ruby more suitable to pervasive and relatively transparent use of metaprogramming.
At the same time, while this flexibility and the Ruby community’s tendency to use it for metaprogramming can facilitate aesthetically pleasing code, they can also create stylistic variation in how the language is used, and obscure the mechanisms by which code actually works. Python’s more restrictive syntax is intentionally designed to steer developers towards one canonical “pythonic” style to improve accessibility and comprehension.

e/ Style
Ruby code is organized into blocks, with blocks starting with various constructs and ending with the keyword “end”. Python code is indentation-sensitive, with successively larger indentation meaning tighter (nested) scopes. Python’s syntax has been described as executable pseudocode.

f/ Functional Programming
Both languages support some functional programming constructs, but Ruby is arguably better suited to a functional programming style. Lambdas in Python are generally very short, because lambdas in Python are restricted to expressions and cannot contain statements. Ruby’s lambda support is far more flexible, allowing for lambda expressions of arbitrary length.

g/ Speed
The standard CPython implementation is generally regarded as executing code slightly faster than Ruby.If speed is really an issue for a Python project, you also have the option to use Cython, Pyrex,Pypy (JIT) or the ShedSkin tools to compile your code into C or C++.

j/ Features
Both Python and Ruby are high level application development languages. Each of them is estimated to have a Capers Jones language level of at least 15. Both languages promote test driven development.
Both languages have full Unicode support, although the way that support is implemented varies. Python distinguishes between “Unicode strings” and “byte-strings”. Ruby, on the other hand, treats all strings as byte-strings with a semi-hidden flag which causes problems when dealing with badly-encoded data from third-party sources.
Both Python and Ruby support multithreading. Python has the Global Interpreter Lock (GIL), which negates much of the potential advantage of using threads; Ruby has a comparable Global VM Lock (GVL).
There are a number of functions that are available by default in Ruby but for which in Python it is necessary to import a module from the standard library. Python supports generators and generator expressions.

k/ Community
There are great communities behind both frameworks. Some people believe that Python has a more developed community in terms of libraries suited for data analysis, machine learning, natural language processing, scientific libraries. As for community folks, Python ones are believed to be conservative and afraid of change, while Ruby guys welcome changes and love new shiny stuff even if it breaks older things. Consequently, Python world is more stable, and you can update your installation without much troubles, but that also means new technology is only added very slowly.

l/ Frameworks
There are a number of Web frameworks based on both Ruby and Python. The most notable and leading are Ruby on Rails (Ruby) and Django (Python) based on MVC. Django is more declarative, with it you’ll have a clearer understanding of what’s actually going on. It lets you specify most configuration details yourself. Django creates a much simpler project structure. On the other hand, the centerpiece of Rails’s philosophy is called convention over configuration. Rails provides you with more defaults.

m/ Popularity
Python is generally more widely used than Ruby, according to most measures, but in the wake of the rising popularity of the Ruby on Rails Web application development framework Ruby’s popularity too has seen rapid growth.
Python is more mature general purpose nature vs Ruby’s more niche (Rails) usage. Python is stronger and sees use in automating system administration and software development, web application development, data manipulation, analyzing scientific data (with help of numpy, scipy, and matplotlib modules), biostatistics, and teaching introductory computer science and programming. Ruby+Rails holds a slight edge over Python+Django for web development and sees use in general programming, and has more mindshare.
In terms of cloud deployment, Python can run on Google-Cloud (Google-App engine). Though Ruby has very strong cloud deployment options in the shape of Heroku and Engine Yard.

Would you prefer Python or Ruby over PHP for implementation of your web project? And is it indeed a philosophy that you chose while selecting between Python and Ruby? Interested to hear your thoughts.

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

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

About five years ago, no one had heard about jQuery. Today, we can say for sure, it is the most popular Javascript library in the world. The statistics clearly says for that fact: in the year 2012 jQuery was used by more than 50% of the top 10,000 websites in the world. That’s a massive endorsement by the world’s web developers :) This kind of widespread adoption is rare for JavaScript libraries, even unprecedented. And the question is: what makes jQuery better than using one of the other (also excellent) JavaScript libraries? There certainly should be reasons for this. Let`s take a look at several of them:

- jQuery has vibrant and helpful community and it is easy to learn. jQuery has very good documentation, in addition there is a great number of tutorials on the web demonstrating jQuery usage. If you encounter a problem, you can ask a question on any web development forum and there will be a large development community waiting to help you :) . Lots of people not only use it but also write tutorials, share their code, make plugins. Also jQuery has a very low learning curve.

- Widespread adoption. Countless big players on the Web are using jQuery: IBM, Netflix, Google (which both uses and hosts the jQuery library), and Microsoft, which now includes jQuery with its MVC framework and works with the open-source jQuery project to contribute new features to the jQuery library. Also there are thousands of big sites that use jQuery: among them are WordPress.com, Pinterest, Reddit, MSN.com, Amazon, Yandex, Microsoft.com, Instagram, Slideshare, the list can go further and further

- Cross-browser Compatibility. Cross-browser compatibility of jQuery is very successful. Most of the code you write will run exactly the same on all the major browsers. In fact, one of the biggest challenges in Ajax/JavaScript programming is cross-browser inconsistencies – it may drive the developer mad. For example, a design that renders perfectly on Internet Explorer , may not run that well on Mozilla Firefox,. So JQuery “fixed” this issue

- JQuery is simple. jQuery objects are chainable. JQuery objects return other jQuery objects and it is possible to perform additional operations in a chain. There is no need to iterate every object one by one.

- Small and clever core library. The jQuery core library is only about 24KB in size (Minified and Gzipped) so it can be easily included into your application and it`s very fast as well. That is due to the fact that a lot of fairly common functionality has been omitted from the jQuery core library, and relegated to the realm of the plugin. Also developers have even a smaller alternative: Sizzle. Sizzle library is 4 KB and it’s simplified just to be used for css selection.

- Great number of plug-ins. The reason of why there are so much jQuery plugins is that jQuery is designed to be pluggable. By including only a core set of features while providing a framework for extending the library, jQuery team made it easy to create plugins that can be reused in all jQuery projects as well as can be shared with other developers.

- CSS3 Selectors Compliant: jQuery fully supports the CSS3 selector specification.

- jQuery UI. jQuery User Interface separates out higher-level constructs and is packaged into a neat library that sits on top of jQuery. UI capabilities might not be stronger than some other libraries such as ExtJs but it’s getting better.

Hope these facts will be of use to you. Of course, the things I listed here might not include all the good points about jQuery and you may add your own points to the list :)
Thanks in advance!

Best Regards,
Anna Kozik – Business Development Manager (LI page)
Anna.Kozik@altabel.com |skype id: kozik_anna
Altabel Group – Professional Software Development

The Android ecosystem has become a dominant force in 2012. Here’s how I see it growing in the coming year.
Brace yourselves: 2013 is upon us, and that means a whole new generation of Android devices, rumors, and expectations.

Android will have a strong showing at CES (Consumer Electronics Show), and the next few months will be littered with new smartphones and tablets. Let’s take a look at some of the trends we can expect in the Android space over the coming year.

This article will touch on many trends in the Android ecosystem, including hardware advancements, vendor decisions, and key events of the year. Given the sheer number of players in the space, there will be much to look forward to in the ever-evolving Android landscape. Indeed, much could be said about any one of these aspects of Android, but we will address them here in broader terms.

Screen size will sharpen and grow

Not long ago, most smartphone screens didn’t exceed 4 inches. Up until the HTC Evo 4G, most Android phones were had 3.2-inch and 3.5-inch displays. Now, thanks to popular handsets such as the Galaxy S3 (4.8 inches) and Galaxy Note 2 (5.5 inches), consumers are becoming used to much larger screens. We’ll continue to see all sorts of screen sizes in 2013, but the standard high-end experience will fall in the vicinity of 4.5 inches. Those of us who are moving into our second and third Android device will expect something at least as big as our current model.
Beyond size, resolution will sharpen. HTC had a leg up with the Droid DNA with a 1080p (versus 720p) resolution, but now nearly every handset maker you can think of is reportedly working on their own 5-inch 1080p HD display for their premium products. Whether you place a lot of importance on pixel density or not, expect screen resolution to be a big buzzword in 2013.

Quad-core will multiply

If you listen to companies such as Qualcomm and Nvidia, then you’re well aware of the fact that quad-core is the new spec hotness, and Android is the vanguard of competition among handset makers all vying for your little green Android dollars.
Gone are the days of big dual-core announcements. If you don’t come to the table with at least four cores of mobile prowess, then you’re not really expecting to compete on the high-end. We should anticipate that the big devices of the coming year will have quad-core 1.5GHz processors or higher, with some even hitting 2.0GHz by the year’s end. Of course, the fight for faster processors might only be relevant on paper; real world practicality is a different animal. It’s one thing to tout the impressive clock speeds or point to a benchmark, but showing the benefits to end users is the most important win.

Play a lot of 3D games? You definitely care about who makes your phone’s CPU. Just want to see what this whole Android thing is all about? Jump in wherever you want, you’ll be just fine.

One area where we may see more improvements is in the phone’s memory and storage. If the previous year saw 2GB RAM emerge for the top-of-the-line memory experience, next year may see us inching toward 3GB RAM. Storage capacities for Android phones (and all phones) will creep up in 2013 as well, yielding 32GB as the standard for mid-range and 64GB becoming common among high-end devices. This will be especially true for those manufacturers opting for internal batteries and removal of external storage, and I expect to see the first handset with 128GB internal storage appear before 2013 is out.

Entry-level phones will benefit

You have to appreciate the trickle-down effect of technology as today’s top devices quickly become tomorrow’s mid-range experience. With that in mind, the $50-$100 Android smartphone of 2013 will be quite an impressive piece of hardware.
Dual-core processors should become the norm for your “basic” Android phone as single-core stuff gets pushed aside. The same may be said of the no-contract handsets, as we’ll continually get more for our money.
As every carrier scrambles to build out its next-gen data network, 4G LTE will be commonplace in Android smartphones. Sure, we’ll get the occasional 3G product every once in a while, but that will diminish with time. This is not to say that 2013 will be the end of 3G Android, but the days of touting 4G LTE as a special feature will pass.

Popularized technologies

There is always a chance that we’ll see a 3D experience in an Android phone or two, but I have the feeling this is one technology that won’t take off. I’ve yet to run into someone who wants or needs 3D graphics in their mobile device. Sure, it’s a cool feature to show off once in a while, but we’re just not ready to adopt this baby. I get the feeling that we’ll see a new surge in NFC-enabled accessories and technologies in the coming wave of tech conferences. The idea of tap-to-play speakers or media players doesn’t seem like much of a stretch for this year’s biggest mobile conferences, CES in January and Mobile World Congress in late February.
Perhaps the biggest issue facing smartphones with large displays and super-fast processors is battery life. Nobody wants to put their phone away to preserve juice; we bought that big screen for a reason.
Looking ahead to the New Year, we expect to see more handsets come with internal and/or higher capacity batteries. The Droid Razr Maxx HD is still the benchmark for long-lasting batteries, but we should see the gap narrow. To that end, we may see less emphasis on “world’s thinnest” or “lightest” claims.

One device around the world

I cannot tell you how pleased I was when I learned that Samsung was going to adopt one singular form factor for the Galaxy S3 and Galaxy Note 2 across countries and carriers. I’m sure that a number of accessory makers were quite happy with the decision as well. Samsung will employ the same strategy for the Galaxy S4 and will likely have records sales again in the New Year.
As far as other companies going this route, HTC today seems to be the closest. I wouldn’t be surprised if its next flagship model were to hit multiple carriers with a single design. As nice as it was to have fewer models to choose from in the One series, it was still confusing to keep up with the various suffixes — One X, One X+, Evo 4G LTE. “Does my carrier offer that one? What’s the difference between this and that?” Along those lines, LG also seems to be slowly headed in this direction with the Optimus line.

Android comes to new territories

The Samsung Galaxy Camera wasn’t the first digital camera to utilize Android, but the first to tie into carriers.
Nikon, Polaroid, and other camera-makers will dabble a bit with Android backbones and we’ll see smarter shooters in 2013. Pricing will need to come down for mass adoption; however, we will see carriers selling connected cameras in retail stores and online.
We will also see more kid-centric tablets and devices with Android under the hood in the next year. We might as well get used to the fact that Toys R Us and Walmart are going to offer $99 Android tablets.
Once the price point of a generic, knock-off tablet, the $100-$200 price range now offers a decent experience for most. Come this time next year, it will not be strange to see a house with even more Android tablets for a range of age groups.
Shortly after Android became a recognized term in the mobile space; we saw the platform arriving in various electronic devices including microwaves and washing machines.
I don’t think we’ll find too much of that in 2013, but it would not surprise me to see a refrigerator or appliance with a custom touch interface that runs Android. Not a full-blown experience, mind you, but something that gives hardware-makers more flexibility.
There is a chance that we’ll see more Android in the automobile in 2013, but it’ll have competition from RIM’s QNX OS. This won’t be a replicated tablet-like experience with full-on Google Play support but something a little smarter than what we have today. It is easy to picture a 7-inch display that lets users hop from stereo to diagnostics to Google Maps.
Another area that would work well is embedding a tablet in the back of the driver and passenger seat. With more cars offering Wi-Fi connectivity over time, a connected device just makes sense. Don’t be surprised if someone introduces a backseat experience that includes access to social networks as well as casual games such as checkers for road trips. For added fun, pair your Bluetooth game controller and dive into a 3D shooter.

Google I/O and major releases

If the last few years are any indicator, there will be at least five key moments for Android in 2013, starting with trade shows: CES in early January, the international Mobile World Congress in late February, and CTIA in late May. Samsung is also expected to launch its Galaxy S4 flagship phone at a standalone press event, if we follow 2012′s model.
Android’s background OS will continue to gain speed, and the company will introduce new features that again pull away from iOS to set the industry pace. We don’t know much about Android 5.0 quite yet, but we’ll assuredly discover bits and pieces of upcoming features in the months just before Google I/O — especially if Google releases a new Nexus device or two to go along with the latest software build.

2013 will certainly be an exciting year for Android, with the mobile OS surely maintaining its mobile lead.

Kind regards,
Polina Mikhan – Business Development Manager (LI page)
Polina.Mikhan@altabel.com
Altabel Group – Professional Software Development

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 :)

Kind regards,
Aliona Kavalevich – Business Development Manager (LI page)
Aliona.Kavalevich@altabel.com
Altabel Group – Professional Software Development