-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Issues: futurice/android-best-practices
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Recommend use of MVP/MVVM/MVI patterns
2018
#150
opened Jul 16, 2017 by
peter-tackage
updated Mar 14, 2018
Revisit id, string, color and dimensions resource naming convention advice
2018
#154
opened Jul 16, 2017 by
peter-tackage
updated Feb 5, 2018
Revise our recommendations for persistence storage
2018
#165
opened Jul 16, 2017 by
peter-tackage
updated Jan 11, 2018
Investigate different format for README
2018
#168
opened Jul 17, 2017 by
peter-tackage
updated Aug 23, 2017
Update Testing Section
2018
PR welcome
testing
todo
#114
opened Jun 18, 2016 by
peter-tackage
updated Jul 16, 2017
Encourage sensible use of Android Support Annotations
2018
#163
opened Jul 16, 2017 by
peter-tackage
updated Jul 16, 2017
Recommend Dependency Injection using Dagger 2
2018
#157
opened Jul 16, 2017 by
peter-tackage
updated Jul 16, 2017
Add collaboration with designers best practices
2018
#156
opened Jul 16, 2017 by
peter-tackage
updated Jul 16, 2017
Revisit advice for keeping XML layouts neat
2018
#153
opened Jul 16, 2017 by
peter-tackage
updated Jul 16, 2017
Add advice for app modularization
2018
#149
opened Jul 16, 2017 by
peter-tackage
updated Jul 16, 2017
Use RESTMock for mocking Retrofit REST services
PR welcome
#116
opened Jun 21, 2016 by
bryant1410
updated Oct 2, 2016
Fragment advice is misleading.
bug
PR welcome
#10
opened Oct 29, 2014 by
jacobtabak
updated Oct 2, 2016
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.