Showing posts with label Developer Android. Show all posts
Showing posts with label Developer Android. Show all posts

Friday, April 3, 2015

5 Steps to Scale Your Android Development

As Android developers, you must have thought a lot about how to scale your Android development processes to ensure that our code is clean and bug-free. While there are no perfect solutions as to how to scale your Android practice, there are general standards that can help you greatly.

1. Keep Things Modular

Keep Objects and classes on tasks they were designed for. For instance, don’t try and perform network tasks in a Datastore class, and the like. The more you separate your logic, the easier it will be to update individual classes later. A good rule of thumb is to keep your method sizes less than 50 lines and your classes less than a few hundred lines.

2. Implement a Consistent Code Formatter

On Android Studio; you can set up your preferred format style under Preferences/Code Style/Java. You can export it and share it across your team once you have a custom template. Any team member can then apply it to a project, and your code will be automatically rearranged. This will save you hours of time and improve readability.

3. Test your code throughout your Android development project

Unit tests are a key part of implementing a test-driven development strategy (TDD). This is absolute necessary to ensure that your code performs the way you expect it to. There’s a minefield of useful information regarding unit testing on Google’s Android Developer site.

4. Add Automated Code Checking.

There are several tools out there to help you code and make sure that you are following the industry’s best practices. The most common ones are PMD, FindBugs, and Checkstyle. You could learn from GitHub repo of as to how to implement FindBugs, Checkstyle, and PMD checks in your app.

5. Go With an MVP Approach.

Using an MVP method in development means separating the Model, View, and Presenter in your code (not to be confused with ‘Minimum viable product’). This is similar to the MVC pattern that’s talked about in iOS.

The fundamental idea is that the View layer should never contact the Model layer directly — because that’s what the Presenter is for. In dissecting the presentation layer from the logic, the way you layout the data on screen becomes modularized and separated from how you pull the data from a server or a database. This style lends itself to easier testing, higher readability, and more seamless collaboration overall.


Tuesday, March 10, 2015

The Amazing Journey of Android

The Android egg hatched on October 22nd, 2008. Initially, many features that we couldn’t live without today were missing- an on-screen keyboard, multi-touch capability, and paid apps for instance- but the foundation was in place. This article looks at the evolution of Android app development and its improvements over the years from Cupcake to Kitkat.

Android 1.5 Cupcake

Android 1.5 Cupcake featured video recording and upload to Youtube, APIs for creating home screen widgets, support for an on-screen soft keyboard and Android virtual devices (AVDs).

Android 1.6 Donut

Android 1.6 Donut bought new user features: Quick search box, new interface for camera and galleries, battery usage indicator and Google Play updates. Text-to-speech engine was introduced along with expanded support for screen densities and resolutions.

Android 2.0/2.1 Eclairs

The new features in Eclairs were multiple accounts that could be added to a device for email and contact synchronization, including Exchange accounts. Search functionality for all saved SMS and MMS messages. Other upgrades included Android virtual keyboard, refreshed UI with actionable browse and calendar updates.

Android 2.2 Froyo

The main feature of Android 2.2 Froyo was the just-in-time compiler which boosted the speed of the applications over three times. Other features include automatic app updates for both application developers and users, FM Radio and OpenGL improvements.

Android 2.3 Gingerbread

Support for Gyroscope, rotation vector, linear acceleration, gravity, and barometer sensors were the major additions in this update for gaming applications. New UI and keyboard interface was introduced. Other features included near-field communications, front-faced camera support, app manager, copy & paste, better audio for apps, and extra large screen support.

Android 3.0 Honeycomb

New UI designed from the ground-up for tablets. System bar for global status and notifications was introduced. Customizable home screens with recent apps, for easy visual multi-tasking interface was introduced. Improved text selection, with copy and paste with new updates for standard phone apps.

Android 4.0 Icecream Sandwich

Icecream Sandwich was the step into the next gen for Android. It had a much refined and evolved UI, Home screen folders and favourites tray, resizable widgets, New lock screen actions, quick responses for incoming calls, Swipe to dismiss notifications, tasks, and browser tabs.

Android 4.1 Jellybean

Gesture mode for blind, transfer over Android beam, and text traversal in accessibility were some of the feature updates in Jellybean. More improvements were in store for browser, calendar, camera and gallery. Faster, smoother, more responsive with refined UI was another feature.

Android 4.4 Kitkat


4.4 was in a league of its own with its Cloud system, lightweight RAM, Pallet colour, remarkable CPU management, good multi cores and screen orientation. It also came in for much praise for reducing battery consumption.

Tuesday, August 5, 2014

5 Quick Tips to Make an Android App Faster Smoother and More Responsive

We live in a generation where advertisers for applications need to work harder than ever to engage target consumers. Based on which, here are some tips on how to make your Android app faster, smoother and more responsive.

Make Your Android App Faster, Smoother and More Responsive

A smoothly operable interface is a major success factor for apps. While deftly concealing the limits of the technology, making the program responsive to the user is one of the major disciplines. Let’s see what all the factors that affects the speed and performance of an Android app.

·         With the amount of devices and quantity of versions releasing, Android fragmentation really has to be done- not the Android file system.
·         Loading your home screens with live wallpaper and widgets can really slow down your Android, especially an older device. Whereas, in case of having a newer Android mobile device, it is not the widgets but animated wallpaper that lags and mar the battery life despite being quite appealing.
·         Basically, Android does a stellar job in the process management which means there is no use of many task killer applications. You should definitely uninstall any uncooperative applications.
·         The responsiveness of an app plays a vital role. Given that there are tons of photo-shooting apps with a few effects and upload functions out there, why people choose popular apps like Instagram?
·         Android mobile device users who are still using an older version like Gingerbread can install a new browser to see an increase in performance.

Owing to which, the basic trick lies in optimizing the collaboration between development and design and that requires hiring a professional expert in app development. Do you need an Android app build for your business? Openwave Computing LLC offers many types of services in Android Application development that includes Business Applications, Navigation, Social Networking, Lifestyle and Entertainment apps, Multimedia, Education / Learning apps, GPS based applications, Utility Applications, Web Search.