Privacy Policy for NaveenDroid

This is the privacy policy for NaveenDroid developed by Naveen (referred to as "we" or "me"). Naveendroid apps are developed mainly for kids. We value the privacy of both the parents/guardians as well as the kids who are using the apps. Please read the privacy policy below and let us know if you have any questions or other feedback regarding this.

Personal Information:

We do not collect any Personal Information like name, phone number, address, location, kids name etc., from within the app users. The app is completely available offline and no registration is required for using our app. Hence no data in collected by us.

If we do happen to obtain any personal information, including emails or phone numbers obtained through support requests or other correspondence, it will be treated with the strictest confidentiality. Any such personal information will never be shared with any other entities. Any such personal information will be retained towards resolution of the support requests and for future reference if you need support again. We can delete the emails anytime on your request. We use Google's G Suite for Business for our emails.

Internet permissions

Our apps do typically require internet permissions, for the purpose of downloading additional content for the app, showing ads providing links to the app store entry of our other apps and to collect anonymous usage information for analytics as mentioned above.

Age limitations:

We do not knowingly contact or do business with children under 13 years of age. If a parent/guardian becomes aware that a child under the age of 13 has attempted to contact and/or do business with us, please advise us by email at naveenv19@gmail.com so that we may rectify the situation.

In-app purchases:

Our apps do not contain any in-app purchases (IAPs) or Subscriptions.

Advertising:

We may occasionally cross-promote other products of our own within our apps.

Social media:

Our apps do not interact with any social media sites. We may provide links to our own social media sites for the purpose of providing support and product information.

Children's Privacy:

As creators of kids apps, we adhere to The Children's Online Privacy Protection Act (COPPA) (http://www.coppa.org) When it comes to the collection of personal information from children under the age of 13 years old, the Children's Online Privacy Protection Act (COPPA) puts parents in control. The Federal Trade Commission, United States' consumer protection agency, enforces the COPPA Rule, which spells out what operators of websites and online services must do to protect children's privacy and safety online. The privacy of your child is of paramount importance to you and we respect that. We DO NOT ask for or collect any child specific data like name, age, school, etc., anywhere in the apps. We do not let third-parties, including plug-ins collect personally identifiable information from children. The In-App Purchases or Subscription Service are accessible only via the parental gate. Only after you enter the correct answer to the parental question, will the access to the parent page be granted. There are NO third-party advertisements in our app other than Google Admob and any app-related third-party links such as social media pages, support and website are only accessible behind the parental gate and child lock buttons.

Use and Disclosure of Your Information:

We do not collect any PII in any way. There is no input fields in our application:

The anonymous Non-Personal global data that we get for analytics purposes is visible only to our developer team and is strictly for internal analysis to make your app-experience better over time. We do not disclose any of your Personal Information that we may collect but we reserve the right to disclose any of your Personal Information if demanded by law or when disclosure is necessary to protect our rights and/or to satisfy a legal procedure, a lawsuit or a judicial order.

Changes to Privacy Policy:

We reserve the right to modify our Privacy Policy at any time simply by posting such modification on this site and without any other notification. Any such modification will be effective immediately upon posting on this site. The use of the information we collect is always subject to the Privacy Policy that is in effect at the time when this information is collected. You are advised to refer to the Privacy Policy from time to time so that you are always in sync with our current privacy practices.

Contacting Us:

If there are any questions regarding this privacy policy, you may contact us using the information below.

Naveen

Email:naveenv19@gmail.com

This Privacy Policy was last updated on 24th June 2018.

ToDo's before publishing Android app!!

I found this stackoverflow thread a very useful one - tips or todo's before publishing Android app in Google's Play Store,

• Launch your app at the end of the week ( thursday afternoon is usually a good time ) why so ? well, no companies would like to publish an app only 1.5 day before the week end -> too dangerous ( in case there is a problem that needs a quick reaction time )
• Use proguard on your app ( usually, you just have to add this line :proguard.config=proguard.cfg in the default.properties file) this will optmize, shrink and obfuscate your code, very usefull for preventing from code thieves. You don't have to delete any comments, there are automatically deleted at compile time
• Optimize your images ( using Paint.NET, PNGCrush or OptiPNG )
• Optimize your layouts for most of screen sizes. You can doing this by simply changing the screen size while editing a layout in eclipse
• Try/Catch all exceptions on the UI and display a simple toast wich indicate to the user that something wrong happened. In the meantime, retrieve the error with the help the ACRA
• Don't use too much .jar libraries, prefer library projects ( optimize the code size )
• Don't use the Android preferences windows -> that's not really beautiful, even if it's in the Android guidelines, prefer making your own settings windows
• Never show the title of your app (this.requestWindowFeature(Window.FEATURE_NO_TITLE);), and consider using the fullscreen mode (this.getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN, WindowManager.LayoutParams.FLAG_FULLSCREEN);)
• Use either Flurry or Google analytics for future analytics -< try to get as much informations as possible, but don't grab anything that violate the anonymous state of the customer. Don't forget to retrieve exceptions that happen on the user side
• Ask your friends to do monkey test, learning from users usually brings many good things
• Consider publishing your app before having finished all features, you don't already know what your users will want to have in the app
• Add a section "More apps" in your app, that's free ads
• Add a section "send feedback" wich let the user ask for feature or specify some bugs
• Ask your users to translate your app by providing the strings.xml somewhere on the web
• Try your app on each android version with the emulator -> many bugs appear at that moment
• Think about the name of the app -> what keywords would you use to search for your app ? these keywords are the name of your app
• Consider including keywords in the app description
• Be the first to rate your app with 5 stars -> that influence the future users ratings
• Consider using Google to translate your app either for the description, either for the strings.xml or both
• Consider adding an advertising feature in your app such as AdMob
• Instead of providing a paid version, consider doing in-app billing -> user are more likely to in-app pay than pay for a paid version
• Add a change log in the app -> users like to see what changes since the last version
• Add a Thanks section for the users that helped you -> this will influence the users to help you
• Add a "If you like this app, please rate it" link ( to your Android Market's description ) in your app -> you will get more 5 stars
• Consider including a "Tips" or "instructions" section in your app
• Unless it's not possible, Prefer external installation (android:installLocation="preferExternal" in the AndroidManifest.xml)

Eclipse doesn't render layout

After installing the new Android SDK, the graphical layout in Eclipse is blank.. It shows

This version of the rendering library is more recent than your version of ADT plug-in. Please update ADT plug-in.

If you get this message, it means that your ADT is out of date and needs to be updated. Follow the below steps to update it,

1. Click Help > Install New Software.
2. In the Work with field, enter: https://dl-ssl.google.com/android/eclipse/
3. Select Developer Tools / Android Development Tools.
4. Click Next and complete the wizard.

Preventing Android device from going to sleep - programmatically?

To prevent an Android device from going to sleep programmatically,

Call setKeepScreenOn(true) on that View or set the keepScreenOn property to true. This will prevent the screen from going off while the View is on the screen. No special permission required for this.

Margin vs Padding - difference??

Knowing the difference between margins and padding in Android is quite important.

Padding is the space inside the border, between the border and the actual view's content. Note that padding goes completely around the content: there is padding on the top, bottom, right and left sides (which can be independent).

Basically this is relative to your border, if you want to add the space between the elements inside the border (i.e. have the borders touching), you should use the padding property.

Margins are the spaces outside the border, between the border and the other elements next to this view. In the image, the margin is the grey area outside the entire object. Note that, like the padding, the margin goes completely around the content: there are margins on the top, bottom, right, and left sides.

If you want to add the space outside the borders (have the borders apart) you should use the margin property.

An image says more than 1000 words:

 

ClassCastException in FrameLayout - changing

I'd spent quite a lot of time to find out the root cause of ClasscastException when we change the order of views in layout xml..

And found that if we do "Project --> Clean" in Eclipse the problem will be resolved.

Eclipse - is the culprit :)

Admob error in Eclipse? - Android

Eclipse is showing an error in android:configChanges line in my AndroidManifest.xml:

<activity android:name="com.google.ads.AdActivity"
              android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"></activity>

and the error is,

error: Error: String types not allowed (at 'configChanges' with value 'keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize').

I resolved it by setting target=android-13 in project.properties file.. After changing it don't forget to do Project-> Clean 

If you would like to know how to make use of Admob in your Android app, you can take a look at this tutorial..

http://www.monkeycoder.co.nz/Community/posts.php?topic=1121