Best
Practices for Developer Coding skills and Naming convention:
2.)
Package name must not contains Android market keywords or Google api
keywords. It’s must be com.<Companyname>.<Application
Name>.
Eg.
Com.halosys.tvanytime
com.adobe.reader
(Adobe Reader)
com.adobe.photoshop
(Adobe Photoshop)
(3.)Class
name must start with its own core functionality like HomeActivity.
If
class contains it’s subclasses in it’s stack then child class
name must be
HomeActivity1,
HomeActivity2 ….
HomeActivity2
(Not use name like home_detail_screen etc.)
(4.)
variable name must contains functionality of it’s own use case.
Eg.
Boolean activityFlag;
String
usernametf1;
Float
submitcal;
Button
submitbtn,
ImageButton
imgShowbtn;
(5.)
Functions / Methods name must be contains with basic functionality
name:
SubscriptionCalculation()
LocationCalculation()
(6.)Always
try to use concept of OOPs. Basically method-reusability, class
reusability.
(7.)Not
use more static variables , if using in java then must release them.
(8.)
if you inhering the code from web then need to change the naming
convention of variables, classes and methods for that particular
block.
(9.)Try
to use Async task classes always Private mode.
(10.)Need
to commented each method of block with that basic functionality.
(11.)Always
try to best way for file handling in java. Always close the stream or
refresh them also.Try to free gc also when finishing the activity.
(12.)
Try to put block of code with one module package.
Com.halosys.tvanytime.facebook
(13.)Must
import think in case of sqlite, always close the database and
cursor.try to always use finally statement.
(14.)
Image name must contains with that function name:
Eg.
Submitimg.png
(15.)In
case of java, one work have different ways of solution here always
try to use best one alternate solution like case of :
Dbhandling
ApiFramework
Native
Interface
Etc.
(16.)Event
Listener contains four types of handling try to always access
ui-thread for access ID.
(17.)Always
try to run a thread in save mode in coding, otherwise app crash.
(18.)Always
use Stack concept for handling view stack.
Thanks,
Naveen
Kumar
