6 NEW YEAR’S RESOLUTIONS FOR MOBILE APP DEVELOPERS
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
6 NEW YEAR’S RESOLUTIONS FOR MOBILE APP DEVELOPERS
#1: Refactor Your Code ASAP
#2: Comment, Comment, Comment (inline your code)
#3: Dude, Why My App Keeps Crashing?
#4: App Permissions and Self Control
#5: Be Kind, Rewind
#6: Hanging by a Thread
TABLE OF CONTENTS
#1: REFACTOR YOUR CODE ASAP
When you’re writing a method or a class, earth-shattering in brilliance or as trivial as they come – refactor.
If you’re copying code from someplace else in your project –build a method out of it.
If you’ve hardcoded a number or a string, any property of any significant – They belong in constants.
Try to minimize code duplication via generics, inheritance, etc.
It’s so much easier to take action on the fly than in retrospective.
Example of Simple Refactoring: Before and After
#2: COMMENT, COMMENT, COMMENT (INLINE YOUR CODE)
Document and explain every line of your code.
The only exception to the above is if the comment is repetitive of a method’s name when invoking it.
Keep your comments short and concise.
If you’re handling some extreme case scenario you’ve encountered, use it as an example.
Show your users you care by hearing their feedback.
Many SDKs companies offer app developers crash reporting tools and analytics, use them!
Learn what your problems are, and attempt to fix them.
#3: DUDE, WHY MY APP KEEPS CRASHING?
#4: APP PERMISSIONS AND SELF CONTROL
Private data gathered by so many companies and gets passed around, sold from one entity to another – be responsible and sensitive.
Don’t request unnecessary permissions or you’ll end up scaring away your potential users.
#5: BE KIND, REWIND
Simplify your app menus or options. Make your users comfortable.
Consider how much battery your app is consuming (usually by excessive location accesses).
Consider how much private data you’re collecting.
Move unnecessary heavy networkconsumption to Wi-Fi only .
IMPROVE YOUR USER EXPERIENCE:
#6: HANGING BY A THREAD
When you write a piece of code, stop to think:“Can this be run concurrently or in parallel by more than a single thread?”
When in doubt, remove doubt bymaking your code thread-safe. consider using concurrency libraries and structures.
SafeDK is your companion for the entire development journey:
from finding the right SDKs, through safe integration, to ongoing
monitoring and real-time control.
Learn more about our useful tools
Happy 2016!
Related Documents
