Author Archives: Hussain Fakhruddin

Google Nexus 5: Not Everything Is Right About It!

According to reports, the first batch of Nexus 5 (32 GB) phones was sold out within a week of its launch. Favorable reviews have also coupled with the mighty impressive sales numbers of this handset. However, it does have certain shortcomings – and we highlight them here.

The initial sales figures of the Google Nexus 5, officially launched on the 31st of October last year, compares favorably with that of the super-successful iPhone 5S. The reviews of the Google-LG smartphone (powered by Android Kitkat) have been overwhelmingly positive too – among users as well as sites like CNET. However, fact that the device is a hit does not mask the few problems that it is plagued by. Let us here highlight these glitches, without which the Nexus 5 would have been an even better handset:

  1. Unreliable connectivity with wi-fi networks – The wi-fi settings of the Nexus 5 are not particularly stable, and there have been complaints of frequent connection drops on it. This, in turn, has made the task of using software developed by even top mobile apps companies on it a rather tricky task. Putting the phone on Airplane Mode and then back to General generally restores the connection. In certain cases, the phone has to be rebooted – for getting wireless internet access.

  2. No option for battery replacement – Google Nexus 4 had a glass back that did not allow users to replace the phone battery, and the plastic shell rear of its successor does not provide this option either. Problems can arise when the pre-inserted lithium polymer batteries start losing their efficiency – after an extended period of usage. On the brighter side though, since the battery is non-removable, the device capacity is relatively high.

  3. Battery life is a headache – Ah, the eternal bane of all smartphones out there. While not strikingly bad, the 2300 mAh battery of the Nexus 5 is nothing to write home about either. Google executives, as well as general mobile app developers, have demonstrated that slightly more battery juice can be generated, by deleting unnecessary applications, and putting the phone on standby (whenever it is not being used).

  4. Camera features – The 8 MP camera of Google’s flagship handset is decent enough (probably the best in the entire Nexus series) – but it can’t hold a candle to high-clarity iPhone 5S camera. The optical image stabilization feature, introduced in Nexus 5 for the first time, does not always prevent pictures getting blurred, at least during the first few attempts. The shutter speed is impressive though – and there is always the chance that there will be at least one ‘perfect’ snap, along with the other ‘defective’ ones.

  5. Loose power button? – Probably, if the slight knocking sounds near the button area whenever the handset is moved is anything to go by. It is always a good idea for Nexus 5 users to get a protective case for the phone. There have also been cases (rather rare) of the power button being too loose – necessitating owners to look for a replacement handset.

  6. Touchless Control not available – ‘Ok Google’ works on this handset (provided that it is not on standby) – but the device is not supported by any other handsfree technology. At a time when Motorola’s Touchless Control and iPhone’s Siri are proving to be huge hits, and everyone is looking forward to Windows Phone’s Cortana – it would have been great if the Nexus 5 packed in voice control features as well. Among the high-end smartphones currently available, this one is among the most competitively priced – and the lack of handsfree options may well be correlated with its low cost.

  7. Poor sound-quality of videos – Video-based applications created by reputed iPhone app development experts are always fault-free – but videos taken with the Nexus 5 fall way short of such perfection. Most videos have sub-par sound quality, with a low humming/hissing noise accompanying the playback. There are no options to block out external sounds either. Thankfully, there are alternative apps at the Google Play Store – which can more or less address this problem.

  8. Build structure – Make no mistake, the relatively tougher body of Google Nexus 5 has definitely contributed to its success. However, the overall build structure of the phone is nothing more than ordinary. Since the rubber rings of the Nexus 4 have been done away with, the plastic body might seem just a tad too slippery. The camera protrudes slightly as well, highlighting that elegance is not a high point of this phone – whatever its other virtues might be.

  9. Poor-quality speakers – Irrespective of whether you are on a call, or are listening to music on the go – you won’t get sharp audio effects on the Nexus 5. The audio has a muffled feel about it, and remains relatively low at all times. Since the speaker is placed right next to the mic (on the bottom edge of the device), users often accidentally block the former with their hands – compounding the problem further. Switching off the virtual surround sound option can make the audio slightly clearer. Modifying the equalizer settings can help somewhat as well.

  10. GPS features not up to the mark – At least when the ‘High Accuracy’ mode under ‘Location -> Settings’ is not activated. Getting a third-party map application is not a viable option either – since the phone’s GPS can drop unexpectedly at times too. The fact that the inaccuracies in the Nexus 5 GPS system are recurring (they often make a comeback even after being apparently ‘fixed’) irks users even more.

 

Rather inexplicably, Google Nexus 5 is not available on Verizon Wireless – and this has, at least to some extent, affected the popularity of the device. At a price of $349 for the 16 GB model), the handset definitely offers more than optimal value-for-money – but that does not imply it is an absolutely perfect smartphone.

Google is planning to release Nexus 6 around July this year – and we can certainly expect it to do away with the shortcomings of its predecessor!

Android Client SDK Errors: Do You Know What The Codes Mean?

Prior to testing, even highly experienced Android developers cannot be fully certain that their codes are error-free. If you have to work with the Android Client SDK, you should have a thorough idea of its error codes and the reasons why they are generated.

With nearly 26 billion Android apps downloaded in all by the end of 2013, there is no scope for doubting the leadership position of this platform over Apple iOS (which is mighty popular in its own right). The Android Software Development Kit (SDK) is relied upon by developers from all over the world, for making glitch-free, functionally advanced applications. However, if you are new in using the kit, the various Android Client SDK Error codes might leave you feeling a bit stumped. We have here explained some of these errors:

  1. Error Code 1 (Could Not Connect To Server) – The most basic Android SDK error – one that occurs either due to an Illegal Argument Exception or a URI Syntax Exception. The software development kit fails to connect with the server system, and this error message is displayed.

  2. Error Code 8 (No Authentication Scheme is Specified) – Experienced programmers from the domain of Java, Android or iPhone app development in India and overseas can generally handle the security configuration project in their codes without any errors – but novices have to be wary of this error. In case they forget to provide a correctly specified authentication scheme for the project, this error would be generated and the program would be stalled.

  3. Error Code 22 (Service Domain Mismatch) – Unless you are careful enough while creating the Single Sign-On (SSO) application of codes, this error message might get flashed. The problem comes up when the server-side domain of the application does not match with that from the client side. As a result of the mismatch, the necessary authentication procedure is invalidated/rejected.

  4. Error Code 17 (Tokens Not Available) – Professional mobile app developers and testers invariably work with web browsers that are customized for SSO authentication. In case the OAM_ID is not provided when a protected/secure URL on such a browser is accessed, this error is generated. Also, if you do not specifically set the the MobileOAMAuthentication, the ‘R.string.tokenNotAvailable’ message would be displayed.

  5. Error Code 24 (APP Signature Invalid) – All the business objects and applications called in the Android Client SDK codes have to be validated. Whenever the single sign-on is not able to perform this validation task, this exception is thrown. If you face this error, you would probably need to check the built app signature for errors.

  6. Error Code 3 (Invalid Username/Password) – Just as in the Google Drive SDK, in the Android toolkit too – server responses can be unauthorized (code: 401). That, in turn, results in this error message. Of course, if you do not declare a username and password before trying to authenticate server-side interactions, the UN_PWD_INVALID message would be flashed. A common error among coding newbies – and it can be fixed easily.

  7. Error Code 10 (User Authentication Failed) – Irrespective of whether you are creating programs for Android apps, or are simply writing codes for web applications – it is of essence to ensure that there are no internal errors in the selected server. Presence of such errors can stop the program-building, and a complete testing of the server would be necessary. Note that, this scenario is different from Error Code 8, which is invoked when the required authentication scheme is not declared/specified.

  8. Error Code 25 (Initialization Failed) – Before you start working with the Android SDK, it would be a good idea to read through all the application-initialization guidelines carefully. According to mobile application development trainers, even if a single mandatory field is not supplied, this initialization failure can result. Once you call an application through an appropriate URL scheme, make it a point to declare all the necessary fields.

  9. Error Code 12 (Unable To Open RP Authentication URL) – Google’s software development kit has all the tools required for seamless construction of the RP login files. However, it might happen that the login id has errors – leading up to this coding problem. The construct procedure can be resumed only after the URL is debugged.

  10. Error Code 6 (Device Not Authenticated) – There is a built-in RestAuthenticationService in the Android SDK, which parses for tokens for the requisite device registration. As soon as the authentication is detected to be invalid, the coder is alerted that no social and/or mobile server has yet been connected to the concerned device.

  11. Error Code 16 (Setup Failed MS) – Configuration errors lie at the root of this relatively frequent error. Whenever the service domain or the application ID is left empty, the app profile cannot be downloaded from the server (social or media). You should take a look at the server URL as well.

  12. Error Code 21 (Setup Not Invoked) – The setup API is integral to the entire coding procedure – and if you do not call it via the setup () method, this is the error you will face. The method can be found in the SDK itself, and you only need to declare it as a part of the program.

 

If you are planning to hire mobile app developers who would be proficient in knowledge-based authentication, make sure that the candidates know how ‘challenge answers’ have to be provided. The No Authentication Scheme and the User Canceled Certificate are also errors that can be generated. Being familiar with all possible errors is a vital part of learning Android Client SDK – only then can you debug your program codes quickly and with relative ease.

 

Working With JSON: A Beginner’s Guide

Since 2006, the popularity of JSON has steadily risen among programmers, data analysts, app developers (mobile and web) and other techies around the world. A preliminary overview of some key features of JSON has been presented here.

When JSON services were launched in the final quarter of 2006, few people had envisaged that it would emerge as a viable alternative to XML – within a relatively short span of time. For storing information via programming, and to facilitate data-transfer between the client and server sides, XML still remains the first choice – although JSON is catching up fast. In particular, it has been found that one out of every four mobile app developers prefer using JSON over the relatively more complicated XML. If you too wish to start using JSON (JavaScript Object Notation), the following would serve as a handy guide:

  1. What types of data can be stored on JSON? – Two alternative structures – arrays and objects – can be built on JSON. The total number of data types supported on the information-storing system is five. You can store strings, objects, numbers, arrays and Boolean (i.e., true vs false) information on it.

  2. How is information stored in JSON? – All data, values and attributes in JSON are have to be stored by creating separate objects for them. You can declare any number of properties inside an object. Multiple property pairings have to be comma-separated. Most professional web app and mobile app developers feel that this systematic manner of storing information is one of the key advantages of the framework.

  3. How can you check for code errors? – Program debugging becomes a rather straightforward task, when you use JSON API (preferably, integrated with Google Analytics). Functions can be called to check all probable errors in the XHR responses that are generated. You can even keep track of the frequency of same/similar errors, with the help of customized reports. Not surprisingly, JSON is rapidly becoming a favorite among app testers too!

  4. Using nested objects – Apart from multiple properties within one object, JSON supports the creation of nested objects as well. The same property pairings have to be declared for each of the nested items – and an alert () function is required to access and display any particular property. Remember to close all the second brackets/curly brackets at the end of each nested object.

  5. How to load JSON on application codes? – This is most easily done via AJAX, by creating an $ajax() method. All the feed items would get stored in the JavaScript Object Notation format, and you can export them on your web browser as well (not recommended though). The dataType you select should be ‘jasonp’. Provided that the method is error-free, getting and retrieving data from external files can be done in a seamless manner indeed. The getJSON() method is used for calling data in the right format from the server.

  6. All response codes are not similar – The XHR response codes, obtained through the jQuery.get method vary with the type of values and properties you use in the objects and arrays. There might even be random variations in the responses, in certain cases. For instance, if a string is passed without any value, it would probably not be shown in the XHR file. The broad framework of JSON responses are same, but you need to note down the differences across projects.

  7. What is the eval() function? – Javascript coders from mobile app development companies in India and abroad need to be familiar with the eval () function. It is used to process JSON codes in JavaScript – which ensures that they are interpreted in the correct manner (and not treated as simple text lines). However, a flipside of using this function is that it slows down the overall loading process. Developers have to be wary about hacker attacks on the converted JavaScript codes too.

  8. Do you need an XHTML page? – JSON cannot be used without a XHTML page. You need to make a ‘doctype’ declaration at the very start of the code. In addition, you will also require Javascript file and jQuery. For best coding results, make sure that the jQuery you are using is of the latest version.

  9. Cross-domain usage – Technicians from mobile app companies also highlight the ‘jsonp’ function as yet another high point about JSON. This method basically initiates a systematic callback function – helping programmers get back the codes on the domain(s) of their choice. Most of the alternatives of JSON do not have this user-friendly feature.

  10. Presence of the server is critical for receiving JSON – Just as APACHE does, JSON also throws up a 503 Error code, in case the server has not been called in program. You need to be particularly careful while working with proxy servers. Remember, the response need not necessarily contain JSON – the server-side has to be properly checked to ensure that.

  11. Is JSON tough to learn? – When you are in charge of coding for web, Android or iPhone app development, you can hardly expect any aspect to be ridiculously easy. However, JSON has a relatively short learning curve, and is almost universally referred to be extremely user-friendly. Apart from JavaScript, it is compatible with multiple program languages too.

  12. You can use the JSON Lightbox – JSON is one information storing and parsing tool which helps in adding to the style of the final output as well. After the processing stage, and above the dataType declaration, you need to call the addLB() function, to add a nice lightbox effect to your code. It is not a necessary part of the code – but is often used by professional developers.

Many newbies tend to make mistakes while creating AJAX requests and/or calling functions (e.g., loadFlickr() ) – and it would not be advisable to try to rush through these stages. Combined with JavaScript (after the string verification), JSON is a very powerful and yet simple data storage and calling method for programming and app development. If the recent trends are anything to go by, it is probably well on its way to overtake XML in terms of popularity among developers.

 

The ‘Tasty’ Code Names Of Android OS Versions: What You Need To Know

The name of which dessert will be chosen as the code name of Android 5.0? As debates and discussions on this topic heats up among techies, we take a look back at the previous versions of the Android mobile OS. All of them, of course, had ‘tasty’ code names!

Eclair, Ice Cream Sandwich, Gingerbread, Cupcake…no, we are not talking about a big upcoming dessert party! All of these are the names of the different Android OS versions – which have invariably been named after a ‘tasty treat’ by Google. While the reason behind this naming strategy is not known, it can easily be seen that they follow an alphabetical chronology. With phone software experts, analysts and mobile app developers already starting to guess what the name of the Android 5.0 platform would be, a sneak peek at the timeline of the earlier Android versions would be in order:

  1. Launch of the Google Phone – Google presented the first Android-powered smartphone in the second half of 2007. The first OS version of the platform was simply called Android 1.0, and did not have any code name.

  2. What is the Petit Four? – Even many experienced developers of Android apps are not aware of the Petit Four. This was the name internally given to Android 1.1. It was a small-scale upgrade over version 1.0 – and general public, understandably, did not get a chance to get familiar with the Petit Four name.

  3. The number convention – The manner in which the succeeding Android versions are numbered is pretty simple. Every major release (complete with new developer APIs) are assigned a whole number. Minor bug-fixes and upgrades are released as decimal points. Most of these minor upgrades do not have code names.

  4. The first popular Android code name – ‘Cupcake’ was the name of Android 1.5, which was officially released in April 2009. Initially, the in-house Google personnel toyed with the idea of calling it Android 1.2 – but they later went ahead with 1.5 and the first-ever ‘tasty treat’ code name. After all, this was a major upgrade!

  5. Getting rid of the rebooting bugs – Android Cupcake was revolutionary enough, but the reviews from mobile app development companies and software developers were not uniformly positive. The main bone of contention was the rebooting error in the operating system. To do away the problem, Google released Android 1.6 (based on API 4) – which also had superior imaging and video capabilities. This version was named ‘Donut’.

  6. Android code-names have a broad similarity with those of Apple OS platforms – Google loves dessert names, just like Apple has a fondness for the names of the various species of wild cats. The Mac OS X Lion was preceded by version codenames like Leopard, Panther, Cheetah and Puma. According to both Android and Apple experts, such distinctive names add to the brand personality of their OS software.

  7. Arrival of the Eclair – In October 2009 (not much of an interval between the releases at all), the Android 2.0 SDK hit the markets. It was named ‘Eclair’, and boasted of excellent multi-touch options and Bluetooth 2.1 support. The camera zooming features were also taken up by a few notches. A small bug-fix upgrade, Android 2.0.1, came along two months later. Keeping with the naming convention, it did not have a separate codename.

  8. Android API 7 was not separately named either – Instead, it was released as Android 2.1X. Certain mobile app developers and technicians refer to this update as Eclair MR1 as well. This 2010 release was mostly a corrective one, for fixing the bugs on API 6.

  9. Did Android violate the norm of dessert names with version 2.2? – ‘Froyo’, at first, might not seem to be the name of a dessert. A closer study would make one release that Google had simply chosen a shorter, catchier form of ‘frozen yogurt’ as the codename for this OS version. Google Chrome and Flash compatibility, and just-in-time (JIT) compilation were among the high points of Android Froyo.

  10. And then, there was Gingerbread – Not only as the code name of the Android 2.3, released at the end of 2010. A tall Gingerbread man was built at the time, on the Mountain View headquarters of Google as well (the height being almost 15 feet!). In fact, the California campus has interesting statues of all the desserts that have been used as Android OS codenames.

  11. Honeycomb and Ice Cream Sandwich – Android Gingerbread ended its run with version 2.3.7 (API 10), and it was succeeded by the Honeycomb OS. The latter covered 3 API levels (11-13), and was the name for Android versions 3.1, 3.2 and 3.3. The code name ‘Ice Cream Sandwich’ debuted with Android 4.0.1, in October 2011. The Samsung Galaxy Nexus was one of the first phones to implement this OS platform. The technical specs of Ice Cream Sandwich were appreciated by experts from Android app development companies from all over. API 14 and API 15 (Android 4.0.3 and 4.0.4) shared the same codename.

  12. Nexus 7 came with with Android Jellybean – Android 4.1 was easily the Google mobile OS with the best user-interface (UI). Internally referred to as ‘Project Butter’, Jellybean was released in mid-2012, and went to on to cover API levels 16, 17 and 18. The last of them, Android 4.3, came with the punchline – ‘an even sweeter Jellybean’. Users, on the most part, agreed!

  13. Kitkat is the latest – We have already reached the letter ‘K’ in the English alphabet, and Google chose the name ‘Kitkat’ for the Android 4.4 platform. It has API level 19, and offers compatibility with a much larger range of devices (including low-RAM ones) than Jellybean. There was some conjecture that Kitkat would be the name of Android 5.0 – but the plan was finally shelved.

 

The date when Google indeed announces the next major version of the Android OS cannot be too far now. General researchers and techies from mobile app companies feel that ‘Lemon Meringue Pie’ or ‘Lollipop’ would be the codename of Android 5.0. Google might face a problem once it reaches the letter ‘Z’ – but for now, it’s fun trying to guess the name of every succeeding Android version!

 

The Sad Tale Of iPhone 5c: Where Did Apple Mess Up?

A comparative study of the market performance of the iPhone 5c and the iPhone 5s would show up stark contrasts. While the latter is currently nearing the iPhone 4s in terms of market share, the response towards the 5c has been, at best, lackluster.

The first attempt of Apple Inc. to develop and market a ‘cheaper’ handset has not been the raging success that it was hyped to be. Company CEO Tim Cook has already admitted this, along with a vague announcement that the sales are picking up. However, the truth remains that – after about six months of its release, the ‘low-cost’ iPhone 5c is still stuck with a market share of just a bit over 6%. This is in stark contrast with the burgeoning popularity of the simultaneously-released iPhone 5s, which have zoomed past iPhone 4 in terms of sales. So, what exactly ails the iPhone 5c? Let’s take a look:

  1. Competition from the way better iPhone 5s – Even a mobile apps company would shy away from releasing similar applications simultaneously – so it’s hard to understand why a bigshot like Apple allowed the iPhone 5c to face the competition from iPhone 5s. The absence of Touch ID was perhaps the most important factor that made the former seem not worth buying, even for many Apple fans. For a few more bucks, they could get the much more advanced 5s.

  2. Contrary to the company image – Microsoft focuses on competitively-priced products, while Apple has always been into making premium computers, mobiles and other gadgets that serve as status symbols – even if they are pricey. iPhone 5c was projected as a ‘cheap’ phone, and that directly went against the long-standing operational policies of the company. More people opted to stay safe, and went for the more expensive models that offered quality-assurance.

  3. Is the iPhone 5c really a low-cost handset? – The price range for the ‘C’ range of iPhones starts from $99, with the 16-GB model bearing a price tag of $549. On average, these figures are only about $100-$130 lower than the prices of iPhone 5s. Since iPhone 5c was supposed to target the lower-end customer segment, the price difference needed to be higher. Of course, whether the amount of $549 is ‘cheap’ is also subjective!

  4. Dwindling interest among buyers – A sample survey conducted by Apple last December revealed that around 9% of all potential buyers were actually interested in purchasing the iPhone 5c. Within the next three months, this figure had dropped to 6%. Clearly people are not too eager to get the low-cost phone model. That, in turn, indicates that iPhone 5c won’t be able to recover from its slow start.

  5. Nothing new on offer – According to experts from the field of iPhone app development in India, a repackaged product has precious little chances of being successful – and the flop show of iPhone 5c indeed bears this out. The device looked more colorful than the original iPhone 5, and that’s about all it offered in terms of newness (along with, maybe, the retina display). In effect, the ‘me-too’ feel about the 5c was too great.

  6. The plastic build of the phone backfired – Jonathan Ive might keep boasting that the iPhone 5c is ‘unapologetically plastic’ – but there’s no denying that this ad strategy has, in fact, been counter-productive. Even if we do not consider the many negative connotations of the word ‘plastic’ (unoriginal, anyone?), Apple should have realized that it was basically making a handset that was too similar to the Samsung Galaxy phones. The plastic structure of the latter has been negatively reviewed, and most people were not even expecting a plastic phone from Apple too.

  7. Was iPhone 5c believed to be the next iPod? – People love to own (and flaunt) a colorful iPod – but buyer behavior cannot be expected to be similar for the much more expensive iPhones. The iPhone 5c was launched in five alternative colors, none of which managed to make quite the splash the company that hoped for. The common practice among iPhone-owners is to keep their device in a proper smartphone case – which makes the color of the phone no longer viewable. A bit of additional market research would have helped Apple to avoid this mistake.

  8. Lack of sober colors – Looking for a black or a sober grey-colored iPhone 5c? You won’t find it! Apart from the white version, the 5C is currently available in green, pink, blue, and yellow(!). Given that black phone models almost invariably have high sales figures, it seems strange that the iPhone 5c did not give that option to customers. Probably a red model would have helped too.

  9. The older processor and device speed – Even if the metal body of iPhone 5s had not killed off the plastic build of iPhone 5c, the latter’s outdated A6 chip was always likely to keep its popularity stunted. The A7/M7 (motion co-processor) of the 5S was way more preferable, particularly due to the much higher device speed it ensured. Als already stated, it did not cost too much extra either!

  10. It was not a flagship device from Apple – iPhone 5 was a flagship device, and it was hugely successful. iPhone 5c is not a similarly featured Apple product, and neither does it pack in the punch in its features and functionality as the iPhone 5s does. Buying the 5c was akin to settling for the second-best alternative for many buyers across the globe, and the poor word-of-mouth publicity pushed it back further.

 

On top of all these factors, iPhone 5c also had to contend with the competition from Android handsets (which, in any case, have an edge over Apple). Remarkably, employees from even dedicated iPhone application development companies are not too eager to start using the 5c anytime in future. Apple might yet manage a remarkable recovery for the iPhone 5c (the recent price-cuts might be the start of such a strategy). With the iPhone 6 looming on the horizon, it is more likely that the 5c would simply be scrapped!

Get Set For Cortana – The High-End Digital Assistant On Windows Phone!

The pre-release buzz about Windows Phone 8.1 is pretty high among general mobile-users, as well as professionals from mobile app companies. Cortana – an all-new mobile virtual assistant – will be making its debut on the platform. It is expected to mount a serious challenge to the popularity of Google Now and Siri.

Android handsets have the efficient Google Now, iPhones have the helpful, witty Siri – and the two voice assistants have been instrumental in enhancing the user-friendliness of the respective mobile platforms. In a bid to keep up, Microsoft has finally decided to implement a similar virtual assistant application (named Cortana) in Windows Phone 8.1 – which is likely to be unveiled within a month or two. Going by the rumors, leaked videos and buzz amongst mobile app developers across the world, the following points about Cortana can be jotted down:

  1. The name – Windows Phone’s much-hyped new voice-assistant shares its name with the central character of Halo – a wildly popular video gaming series. In the game, Cortana has a high level of artificial intelligence, and this would probably be replicated in her mobile version too.

  2. The promise – According to information obtained from The Verge network as well as online videos, Cortana promises to make ‘life a bit easier’ for users. Whether its features indeed manage to rival that of Siri in particular, and iPhone app development in general, remains to be seen though.

  3. The look – Cortana on Windows Phone is expected to carry quite a bit of visual oomph. The digital assistant would take on the figure of a simmering blue female, and there would be a blue ring too – which would get activated whenever Cortana speaks, or even thinks. If you have played Halo 4 before, you probably already have an idea on how Cortana on your smartphone would look like!

  4. Activation – The mobile app designing and features of Cortana have been laid out in a way that, no extra button-presses or screen taps are necessary to activate it. In fact, Cortana will remain active even when the Windows Phone 8.1 is locked. You only have to talk to her, to start getting her responses. Trying to go one up on Siri? Probably!

  5. The first words – After getting the customary ‘Hi, I’m Cortana’ and the promise to make life easier out of the way, the mobile assistant app would proceed to tell users that the latter need to create separate Microsoft accounts. Oh, and she will be able to address mobile-users by their names, nicknames, or even as ‘Master Chief’-s.

  6. Gathering user-information – To compete with Apple’s Siri and Android’s Google Now, Cortana needs to have an intuitive interface and database – and the mobile application development experts at Microsoft have focused on this issue. After you get on the main screen, the assistant will ask you quite a few questions (mostly in multiple-choice formats), about your data-requirements, behavioral traits, and other general topics. Providing customized help is surely the objective of such preliminary questioning.

  7. Privacy concerns – On Windows Phone 8.1, people would have complete freedom of choice about the nature and extent of data they wish to share with Cortana. Prior approvals would be sought by the virtual assistant, before it collects information from your emails, calendars, mobile web history and other sources. It’s up to you to decide how close you will let the blue lady on the phone screen come to your important information databases.

  8. Ability to monitor wi-fi and Bluetooth functions – A common complaint against Siri, received by iPhone application development companies in India and overseas, is that it cannot turn mobile wi-fi and Bluetooth settings on and off. Cortana would probably address this issue (although we can’t be totally certain before the digital assistant makes her debut). It would function in sync with most other controls and functionalities of Windows Phone too.

  9. The search box – The leaked screenshots of Microsoft’s new mobile assistant show a small search box near the bottom of the Cortana screen, with a mic right beside it. People would, in all likelihood, have to speak to that microphone – to spring Cortana into action. Let’s just hope Cortana does not have problems in understanding different accents!

  10. The range of information available – Representatives from mobile application development companies who have caught a sneak peek of Cortana in action, have only positive things to say about its functions. The range of stuff that the Windows Phone assistant can help you with seems impressive enough – ranging right from stock market updates and note-taking, to real-time traffic updates, reminders, and task and appointment-scheduling. There is a small weather widget on the Cortana screen as well.

  11. The Quiet Hours Mode – In Cortana’s final form, this might also be known as the ‘Do Not Disturb’ mode. If you are in an important meeting, or rushing to finish up an assignment – you can activate this mode, and let the virtual assistant take care of all the voice calls and messages for the required time-span. You can even sort the communication modes to be left active under the Quiet Hours mode.

  12. Turning off notifications and suggestions – Much like Google Now, Cortana would focus on providing only relevant, contextual information to users. You would be able to turn off push-notifications, email alerts and/or flight-information – whenever you do not need them. Its purpose is not to disturb you with a deluge of push-notifications – you will get only what you want from the assistant.

The current voice search mechanism on Windows Phone has not been favorably reviewed by most users, and Cortana is almost sure to be a vast improvement. Nokia Moneypenny and Nokia Goldfinger are the devices on which the new mobile OS (and the digital assistant) are expected to make its debut. Provided that it does not botch up things as the initial version of Siri did, and that it remains uniformly user-friendly, Cortana does seem to have the potential to compete with its already established rivals.

 

Let’s just wait and see whether Cortana sizzles or fizzles out, what say?

 

Protecting Intellectual Property Rights: What Mobile App Developers Need To Know

A smartly designed, engaging mobile app is an intellectual property that is owned by its developer company (unless, of course, it is created by an individual). Professional app developers need to be aware of these tips to protect the intellectual property rights of their applications.

Professional mobile app developers cannot afford to ignore the importance of protecting the intellectual rights of the applications they create. A couple of months back, a case of copyright infringement of Android apps was brought to light by the US authorities, with charges being brought against the four alleged criminals. Unless you get all the legal rights on your app concepts and designs, a competitor might simply plagiarize your idea – and eat into your potential clientele. Apart from the creative and technical perspectives, mobile application development has a legal side, and we will give an overview of it here:

  1. Settle ownership issues from the very outset – If you own a mobile apps company, this is something you need to look into at the very start of app development processes. While brainstorming for viable ideas and concepts, make it clear to others that the final rights on the app would remain with the company – and not to any individual developer. The IP address of the standalone PC/computer network would also be a company asset. There should never be any disputes over personal claims.

  2. Be wary while using open source codes – Thanks to the availability of well-stacked open-source program codes and libraries, mobile apps can now be developed quickly and relatively easily. However, indiscriminate usage of open source resources would not be advisable. Often, such open source software comes with certain stipulations and user-restrictions. These, in turn, can compromise the privacy of your apps’ intellectual property rights.

  3. Get a trademark for the name of your apps – To prevent other Android and iPhone application development companies in India or overseas piggyback the popularity of your applications, a registered trademark is essential. It would keep your competitors from choosing identical (or overtly similar) names for their apps. What’s more, the trademark would protect your app icons and logos from being randomly copied as well.

  4. Respect the clauses of license agreements – According to an OpenLogic survey sometime back, it was found that over 70% apps flouted the basic license agreements of the software they were developed with. Remember, you cannot claim the rights on any portion of the code – that has been already published as open-source. Never use any programming code/IDE online, without going through the license documents first.

  5. Keep a written copy of the property rights document – It would be too naive to assume that, just because a you have developed a mobile app – you automatically get all the rights on it. Such intellectual property agreements always have to be finalized in writing. In case you are planning to hire a third-party mobile app developer, make sure that (s)he is prepared to provide the necessary non-competing agreements.

  6. Get your app copyrighted – You need to be on your guard about your original app ideas getting blatantly copied by rival mobile app companies. This is precisely where the importance of copyright protection comes into the picture. Of course, you have to start working on the idea, before applying for a copyright. The entire process of acquiring a copyright on an app does not take long, and is not associated with big expenses either. Of course, you can’t get a copyright on an idea you have only just thought of – there has to be something more substantial!

  7. Do a thorough research before naming your app – Both Google Play Store and Apple iTunes have well over a million apps each. Leading mobile application development companies invariably have a research team, which goes through the trademarks of each of the products at the app store. This, in turn, ensures that the name you choose for your application is not ‘too similar’ with that of an already existing app. In addition, you also need to stay away from names that might hamper the chances of your app getting approved (on iTunes). The recent controversy over the word ‘Flappy’, after the Flappy Bird app was taken down, is a classic example in this regard.

  8. Get your app codes registered – If you do not bother registering the original software codes used at your mobile apps agency, you are basically inviting trouble. In the absence of registration documents, you cannot sue a rival firm – even if it wilfully plagiarizes your app designs/features. You should also find out about the extent of statutory damages you can claim, in case such violations do come to your notice.

  9. Get your best apps patented – Given the rather high costs involved in getting patents, it is neither necessary nor feasible to get such protection for all your applications. Go for patents only for the apps that you genuinely believe would be able to generate (and sustain) high download figures. To keep the expenses under wraps, you can hire a qualified attorney for acquiring the required patents. Copying patented apps is not something fraudulent companies look forward to doing – for the penalties and monetary compensations can be huge. Your best apps would remain well-protected!

  10. Implementing company-wide trade secrets policy – What about the apps for which you have not got patents? The intellectual rights on them (particularly during the early stages of app development) can be protected via company-wide trade secret agreements. The trade secrets should be framed in a manner that, all types of unauthorized public disclosures about the app under production are banned. Promotional pitches, issued by the company, should not fall under the trade secrets policy, however.

Mobile application developers may also have to provide non-competing agreements on apps designed for third-party clients. Make sure that you have taken proper protective measures for the intellectual property rights of apps – before submitting them to the online stores. Developing unique and engaging mobile apps call for considerable creativity and expertise – don’t just let anyone steal your concepts and get away with it!

 

Samsung Galaxy S5 – The Features We Liked

Along with the Sony Experia Z2, the launch of the much-awaited Samsung Galaxy S5 was the most talked-about event at the Mobile World Congress this year (at Barcelona, Spain). Let us here take you through some of the best features of the new smartphone model from the house of Samsung.

Putting an end to weeks of speculation amongst gadget-lovers, Galaxy S5, the latest flagship mobile handset from Samsung, was finally unveiled at the recently-concluded Mobile World Congress (MWC). While there have been murmurs of disappointment over the slightly tacky design features of the new phone model, the overall initial reviews of the latest Samsung device has been mostly positive. We will here list the features of Samsung Galaxy S5 that really come across as impressive:

  1. The improved fingerprint sensor – The Samsung Galaxy phones are not the best when it comes to security features – but the Galaxy S5 does have the potential to turn things around. The high-end sensor of the device can be used to authorize fingerprint validations for mobile transactions. Logging in to mobile apps is also likely to become easier with the sensor. On the phone, fingerprint id can never be removed/duplicated.

  2. The Heart Rate monitor – Rumors have been doing the rounds that iOS 8 would have an exclusive Healthbook app – and Samsung Galaxy S5 is already up for the competition. Just like external medical apps created by mobile application development companies, the Heart Rate Sensor of the phone would allow people to keep track of their heartbeat rate, at all times. More concern for the health of phone-owners currently seem to be what the smartphone biggies are fighting to provide!

  3. Dust-resistance and waterproof properties – Not something new for Samsung Galaxy S4 Active users – for all others, this feature is a relief. No longer would people have to remain constantly apprehensive about a drop of water causing serious damage to their new Galaxy phone. The backside of the handset has a dimpled design, which prevents accumulation of dust. Wiping the phone once every week or so should be enough for keeping it clean.

  4. More powerful battery backup – Nopes, the 2800 mAh battery of Samsung Galaxy S5 will not last for a couple of days – but it certainly would last longer than many similar smartphone models. The Battery Saver Mode, in fact, has been implemented to help users derive that extra bit of battery juice. Provided that you are not using too many mobile apps, you can expect the phone battery to last for at least 24 hours.

  5. Camera – Probably the standout feature of the newly-launched phone. Experts from even iPhone app development companies in India and overseas have expressed their appreciation over the high-clarity 16MP camera of the Galaxy S5, which comes with revolutionary Autofocus and Selective Focus options. Snaps of even fast-moving objects can now be captured, without any problems.

  6. Real-time screen display adjustments – Unlike its predecessors, the display screen of the new Samsung phone has automatic brightness, contrast and color-adjustment features. The display style gets adjusted on the fly, depending on the type of content that is displayed on the mobile screen. The built-in light sensor of the handset indeed lends it a sharper, more interactive feel.

  7. Tie-ups with major apps – More Galaxy Gifts (in the form of apps) – that’s what the newly-launched Galaxy S5 promises to buyers. While definite information on this count is not yet available, the phone is likely to have default tie-ups with many top app development companies across the world. Box, PayPal and LinkedIn are some of the apps that would probably be pre-installed on the device.

  8. The Ultra Power Saving Mode – After (and if!) you buy Samsung Galaxy S5, you might find the display turning fully black-and-white, after it is kept idle for a few minutes. Don’t jump to the conclusion that this is a technical glitch – it happens since the Ultra Power Saving Mode gets automatically activated. Unnecessary apps that might have been running in the background are also closed in this mode. The end result is – less strain on the phone battery. We totally #like!

  9. The Touchwiz user-interface – The feedback on the TouchWiz user-interface of Samsung Galaxy phones have been, till date, rather polarized. The response to the customized TouchWiz UI of the Galaxy S5 is likely to earn more uniform approval though. Obtrusive apps with unnecessary calls for action have been done away with, and the phone apparently makes an attempt to provide users with seamless Android 4.4.2 (Kitkat) mobile experience.

  10. Download booster – Mobile data download speeds are all set to become higher than ever before, on the Galaxy S5 device. In the phone, LTE and wireless (Wi-fi) connectivity can be simultaneously activated, to bolster the pace of downloading by as much as 80% (compared to downloads using either of the two alone). The LTE support in the phone is likely to be available on almost all leading mobile carriers.

 

The private mode of the Samsung Galaxy S5 is yet another noteworthy feature of the phone. Although the increase in screen size is not really significant (5-inches to 5.1-inches), the smooth AMOLED display impresses. Samsung also takes a cue from the Windows Phone – putting in a child mode in the Galaxy S5, which would make downloading and launching mobile apps for kids an absolute breeze. The new Samsung phone does not have any stunning hardware upgrades – but there are enough subtle, user-friendly features which can be instrumental in generating a uniformly enthusiastic response from buyers!

 

Are You An Eclipse User? You Will Find These Tips Useful!

While there is hardly any need to reiterate the popularity of Eclipse among Android developers, not everyone manages to use the plug-in in an optimal manner. In the following discourse, readers will be acquainted with a few handy features of Eclipse that considerably ease the task of application development.

 

On average, over 65% of Java and Android app developers cite Eclipse as the integrated development environment (IDE) of their choice. While the software does come with a host of high-end features, getting a proper grasp on it takes a bit of time – particularly for newbies in this field. There are instances where wannabe techies end up using Eclipse as only a text editor, while going with Intellij or Netbeans IDE, which are perceived to be ‘easier’. We here offer a few pointers that would help professional developers leverage all the built-in capabilities of Eclipse in an effective manner:

  1. Saving the file – While working with Eclipse, mobile app developers and programmers need not keep clicking on the ‘Save’ tab on the toolbar of the application window, after adding/changing a few lines of code. All that they have to do is make sure that the ‘Save automatically before build’ option (under the Preferences tab) is enabled. This might seem a minor feature – but coders can save quite a bit of time by using the auto-save option.

  2. Managing .jar files – Eclipse is by far the best IDE for coders who need to create and maintain multiple .jar files in their JEE or app development programs. The files can be categorized according to their types – and systematically saved under separate User Libraries. For calling the .jar files, these libraries only have to be added to a build path. In a complex, lengthy code, this keeps things from getting cluttered.

  3. Files on split screen – Most leading mobile app development companies in India prefer the usage of Eclipse over, say, Netbeans – precisely due to this feature. On Eclipse, two separate code files can be viewed simultaneously, doing away with the need for toggling between different windows. Once you select ‘New Editor’ (present under ‘Windows’), you can make changes in two locations within the same file.

  4. Common launch configuration option – Yet another easy and time-saving feature for developers. Under Menu, the ‘Launch Configuration Tab’ is present – which allows coders to initiate the configuration stage of their programs in a quick, glitch-free manner. What’s more – they can select their permanent launch option and debugging menu as per their preferences. Eclipse definitely bags high marks in terms of offering user-flexibility.

  5. Assistance to code-typing – Eclipse is much more than a standalone text editor for Android application development experts. However, the holistic typing support it offers deserves a special mention as well. Right from Quick Fix, Refactoring and Assign Parameter, to the Code Completion option – the plug-in makes sure that users do not have to do much of manual typing on their own. That, in turn, lowers the probability of errors creeping into the built codes.

  6. The Ecore tools – The Eclipse Modeling Framework (EMF) project and the standout Ecore tools available in it have received a big thumbs-up from programmers all over. Ecore includes a streamlined visual editor for diagrams, which makes the task of code-modification and/or new file creation (as required under various modeling techniques) rather straightforward. For keeping the program designing and its implementation in sync, using Ecore is a way more convenient option than having to grapple with external UML diagrams.

  7. Managing several projects within a single workspace – The last thing any developer (even an experienced one!) wants while working with multiple Spring and AspectJ environment workspaces is having to memorize the name of the workspace every individual project is stored in. Eclipse offers an easy way out, via the ‘Working Sets’ option (this one is available under Package Explorer, on the top right side of the window). Customized groupings of the various projects can be created – and after that’s done, developers only need to check the ‘Working Sets’ option under the ‘Show’ menu.

  8. Memory space management – The default memory space of an workspace in Eclipse is not always effectively utilized by novice J2EE developers. This generally happens owing to their ignorance about the Permanent Generation (PermGen) memory allocation option, that is available in the plugin. To avoid getting repeated memory error messages, a ‘XX:MaxPermSize’ has to be defined. As codes get lengthier, and using third-party code plugins become essential, this makes sure that developers do not face the ‘Out Of Memory’ problem.

  9. Support for cross-platform application development – Most popular IDE tools offer custom tools for the different operating systems (OS) developers might be working on. Eclipse, however, stands out – thanks to its top-notch support for cross-platform mobile application development coding. From the Preferences menu, the UTF-8 encoding option has to be selected, for creating programs that would run smoothly on all platforms. Coders no longer have to worry about special characters creating a problem.

  10. Keeping imports organized – Many Java programmers stay away from importing files on Eclipse – simply because they feel that making edits in such imported files would render the latter useless. The truth, however, is Eclipse has built-in options to automatically organize all data imports on save (the ‘Organize imports on save’ feature has to be enabled for that). Alternatively, developers can opt for the Shift-Cmd-O (Mac) or Shift-Ctrl-O (Windows), to manually organize the imported files.

  11. Using Step Filters – Be it for Java program testing or a mobile app testing, a focused approach is essential. Eclipse IDE allows users just that – through its well-thought out Step Filtering option. During the debugging phase, step filters make sure that only the actual source codes are displayed – keeping other underlying program techniques hidden. Error-detection and fixing becomes a lot easier, as a result.

 

Eclipse comes with a built-in Perspectives feature (allowing users easy toggling options), which adds to the convenience of app developers. Since Classpath Variables can be defined with ease, individual projects and workspaces can be seamlessly shared with other users as well. There’s no doubting that the learning curve of Eclipse is a slightly steep one – but if one invests enough time to get a hang of it, Eclipse can easily prove its worth as by far the best Android development IDE.

 

Google Glass: Why Is The Initial Response Only Lukewarm?

The tremendously hyped Google Glass was launched last year, with initial user-feedback ranging from mixed to downright unfavorable (except for select geeks). We here analyze why the response to Glass has not been as enthusiastic as Google had hoped it would be.

 

Going by the pre-release hype about Google Glass, it was being hailed as the next big thing in the domain of portable computing. Since its launch in 2013, Glass has become available to many developers and techies in the United States – and surprisingly, the response has not been too positive. A research survey revealed that, only about ten percent of the regular smartphone-users in the country were willing to try out Google Glass, while over 45% of respondents stated that they would never go for it – even if the wearable computer had a lower price tag. Where has Google gone wrong with Glass? Let’s take a look:

  1. Voice command feature disappoints – Apart from limited tapping and swiping options, Google Glass has to be mostly operated via voice commands. Users have reported that, even mildly accented commands led to Glass completely misinterpreting them, and carrying out the wrong functions. Using Google Glass in a room full of chattering people can be a real tough task. The makers had touted Google Glass to be a worthy competitor of iPhone apps in India and abroad – but that’s not going to happen anytime soon.

  2. Google Glass appears to be targeting nerds – Own a Google Glass, and bid your general social life goodbye – or so it seems at present. People have, understandably, felt that it would appear somewhat disrespectful (creepy even!) to actually talk with a friend/colleague, with the Glass plugged to their eyes. In any case, the new gadget encourages users to talk with…well…themselves only, replacing healthy social interactions somewhat.

  3. Suitable only for those with close-cropped hair – To be fair, the neat arrangement of the touchpad, battery and other control sections of Glass on its right-side arm impresses. There’s only one problem – if a user has long hair (at least most females do), (s)he will have no option to tuck it in behind his/her right ear. The hair would have to be kept loose over the touchpad, which can lead to erroneous functions in the gadget.

  4. Google Glass burns a hole in users’ pockets – The initial price-tag of Google Glass is $1500, and it is way too expensive for average users. By the looks of things, Google probably wanted to make a gadget that would double up as a status symbol – just like the high-end apps created by mobile application development companies – but the astoundingly high price-level would keep its appeal limited. Even the ambitious Google Nexus phones failed, and they were priced at much lower levels.

  5. Too much of notifications – Information and real-time updates of practically all types are available on Glass – but that does not necessarily make it a user-friendly product. If anything, the fact that push-notifications keep arriving after every few minutes tends to distract users. Like in iOS devices, there is no way of seamlessly filtering the notifications either. If you buy Google Glass, be prepared to receive notifications – important and unnecessary ones!

  6. Glass puts personal privacy of people at risk – The marketing pitch of Google, while promoting Glass, has been all wrong. The multi-billion company has been harping on how the Glass can snap pictures of anyone, anywhere – or record conversations with any person – and post them in the World Wide Web with so much of ease. The assumption that everyone is dying for such unwanted publicity is a mistaken one, and most people prefer to stay inconspicuous than having random photos of themselves getting posted on the internet.

  7. Taking good photos with Google Glass is a matter of luck – For a gadget that has camera features as its standout function, Google Glass lags behind most smartphone models and camera-based mobile applications. People are supposed to point their nose towards the person/thing that they wish to snap, and take photos with a slight downward angle. There are no options to check a preview before giving the voice command, and the device lacks essential camera settings as well. If Google Glass is to sustain, it needs an upgrade, soon!

  8. The display is far from extraordinary – If you are used to watching high-definition TV and have cell phones with crystal clear displays, Google Glass is bound to come across as a ho-hum product. The display resolution is nothing great, and it is often difficult to even see all the four edges of the view through Glass. Instead of having projector functionality, all that the gadget offers are physical images – and that too, often blurred. People looking for a more immersive viewing experience have, as a result, stayed away.

  9. Battery life is unsatisfactory – If you are very, very careful in your usage of Google Glass, you can expect its battery to last for a grand total of…around eight hours! On the other hand, if you randomly click about and/or use apps on it – you might run out of battery juice on Glass within three to four hours. Most smartphones face criticisms for their low battery backup, but Google Glass performs even worse on this count.

  10. Timeline often gets overloaded quickly – From app-notifications to images and videos, everything on the Google Glass gets stored on the timeline of the device. Initially, this might seem rather convenient – but as soon as the timeline starts getting cluttered, using the Glass becomes a problem. Users are expected to go through elaborate search procedures, to retrieve the media files that they might be looking for at any time.

The general HUD-based user interface of Google Glass has not wowed many users either. Random tests have shown that, activating the Glass can be a time-consuming task as well. The gadget is not suitable for ‘prolonged interactions’ (e.g., watching hour-long television programs). Just like gimmicky apps released by Android and iPhone application development companies in India and overseas, Google Glass has all the potential of being an overhyped failure. Google wins brownie points for bringing an innovative product to the market – but the latter’s functionality leaves much to be desired!