DevelopmentPayment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.

Example result
Code review: a Kotlin Android app and its Java back end
Findings
| # | Where | Severity | Issue |
|---|---|---|---|
| 1 | CheckoutViewModel.kt:88 | High | "Pay" can be tapped twice; there is no idempotency key, so two payments are created. Likely cause of double charges |
| 2 | OrderService.java:142 | High | @Transactional on a private method has no effect; a failed payment leaves the order saved |
| 3 | CartRepository.kt:31 | Medium | Network call on the main thread when the cart opens; causes freezes on slow connections |
| 4 | OrderRepository.java:57 | Medium | Loading items in a loop: 1 + N database queries per order (N+1) |
| 5 | PriceUtils.java:12 | Medium | Money stored as double; rounding errors on totals. Use BigDecimal |
| 6 | SessionManager.kt:19 | Low | A singleton keeps an Activity context; memory leak after rotation |
Fix for finding 1 (Kotlin)
fun pay() {
if (_state.value is Paying) return
_state.value = Paying
viewModelScope.launch {
api.pay(cartId, idempotencyKey = checkoutId)
}
}
The server also stores the key and returns the first result for any repeat request.
What is done well
Clear module boundaries, good test coverage on prices (82%), and consistent naming.
Order of work
Fix 1 and 2 before the campaign (about 1 day), 3 and 4 in the next sprint, 5 and 6 when convenient.
Client: Basketly, a grocery delivery startup; Android app in Kotlin and a Spring Boot back end in Java, about 14,000 lines in the reviewed modules Task: review the checkout flow on both sides before a marketing push; users report rare double charges and app freezes
The client and all details are made up.
About this service
Java and Kotlin code for Android apps and back-end services runs into the same few problems: null values that slip through, work done on the main thread, resources that are never closed and classes that grow to do everything. We read your code, explain how the classes and calls fit together, and mark crashes waiting to happen, lifecycle mistakes on Android and blocking calls in services. Corrected fragments use idiomatic Kotlin or modern Java, depending on what you write in.
What is included
- What you getA written review on the order page: how your classes work together, issues by importance and corrected fragments in Java or Kotlin. Premium adds a plan for splitting oversized classes and screens.
- Stack trace explainedWhere and why it crashed
- Null safetyOptional, ?. and !! checked
- Threads and coroutinesNo blocking on the main thread
- Android lifecycleActivities, fragments, ViewModel use
- Fixed fragmentsIdiomatic Java or Kotlin
How it works
- 1BriefYou paste classes and the stack trace
- 2ReadingWe follow calls between classes
- 3ReviewYou get issues and corrected code
What we need from you
The classes pasted as text or screenshots, Java or Kotlin version, Android or the back-end framework you use, what should happen and the stack trace if it crashes.
We will ask you:
- Java or Kotlin, and which version?
- Is it an Android app or a back-end service?
- What goes wrong, and is there a stack trace?
- What should we focus on most?
Compare packages
| Packages | Basic$15 | Standard$35 | Premium$69 |
|---|---|---|---|
| What is included | Code up to 100 lines | Code up to 400 lines | Up to 1,000 lines with a split plan |
| Deadline | 1 day | 2 days | 3 days |
| Revisions | 1 | 2 | 3 |
| Lines of code | up to 100 | up to 400 | up to 1,000 |
| Corrected fragments | Yes | Yes | Yes |
| Class split plan | No | No | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Do you run my code?
No. We read it carefully and reason about how it behaves, but we do not execute it, so test every suggested fix in your own project.
Can you review my Gradle build errors?
Yes, paste the build file and the full error output. Dependency conflicts are often visible from those alone.
Should I convert my Java code to Kotlin?
We can show how a few of your classes would look in Kotlin and what you would gain, so you can decide with real examples.
Did not find your answer?


