Android App Performance Overhaul
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted11 hours ago
My Java-based productivity app on Android has hit a wall: slow cold starts, janky scrolling, and noticeable battery drain on several test phones. I will hand you the full source code together with the specific devices and OS versions where the problems are easiest to reproduce.
Your first task is to profile the app thoroughly—please rely on Android Studio Profiler, Traceview/Systrace, or any other low-level tools you prefer—to pinpoint concrete bottlenecks (UI thread blocks, memory churn, excessive wake-ups, I/O stalls, etc.). I need hard numbers: baseline metrics before you touch the code and the improved numbers afterward, so the gains are undeniable.
Once you have the data, fix the underlying issues in code. I am open to refactors, lazy loading, background threading, or tighter power-friendly APIs, as long as the behaviour stays intact for users.
Because I don’t want these regressions sneaking back, wrap up with concise engineering notes describing:
• the problems you found and how you solved them
• guidelines or code patterns I should follow (or avoid) to keep performance stable in future updates
Acceptance criteria
• Cold-start time, scroll FPS, and battery usage each show a measurable, documented improvement on the supplied devices
• A before/after profiling report is checked into the repo alongside the code changes
• The prevention notes are clear enough for any team member to apply going forward
Looking forward to seeing the app finally run as smoothly and efficiently as it should.
Your first task is to profile the app thoroughly—please rely on Android Studio Profiler, Traceview/Systrace, or any other low-level tools you prefer—to pinpoint concrete bottlenecks (UI thread blocks, memory churn, excessive wake-ups, I/O stalls, etc.). I need hard numbers: baseline metrics before you touch the code and the improved numbers afterward, so the gains are undeniable.
Once you have the data, fix the underlying issues in code. I am open to refactors, lazy loading, background threading, or tighter power-friendly APIs, as long as the behaviour stays intact for users.
Because I don’t want these regressions sneaking back, wrap up with concise engineering notes describing:
• the problems you found and how you solved them
• guidelines or code patterns I should follow (or avoid) to keep performance stable in future updates
Acceptance criteria
• Cold-start time, scroll FPS, and battery usage each show a measurable, documented improvement on the supplied devices
• A before/after profiling report is checked into the repo alongside the code changes
• The prevention notes are clear enough for any team member to apply going forward
Looking forward to seeing the app finally run as smoothly and efficiently as it should.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.