How Telecom Companies Use Android Development to Grow Faster

// Plain Kotlin - runs with kotlinc or in any Kotlin playground
data class DataPack(
    val name: String,
    val dataGb: Double,
    val validityDays: Int,
    val price: Int        // sample values, not real tariffs
)

fun pricePerGb(pack: DataPack): Double = pack.price / pack.dataGb

fun main() {
    val packs = listOf(
        DataPack("Pack A", 1.5, 28, 300),
        DataPack("Pack B", 2.0, 28, 360),
        DataPack("Pack C", 3.0, 56, 700)
    )
    val best = packs.minByOrNull { pricePerGb(it) }
    for (p in packs) {
        println("${p.name}: %.1f per GB".format(pricePerGb(p)))
    }
    println("Lowest price per GB: ${best?.name}")
}

Self-care home screen - checklist

[ ] Data, calls and SMS left, shown at the top
[ ] Validity end date visible
[ ] One-tap recharge button
[ ] Loads quickly on slow networks
[ ] Shows last updated time
[ ] Works in light and dark mode
[ ] Supports regional languages where possible
[ ] Clear error message when offline

<!-- AndroidManifest.xml (inside <manifest>) -->
<!-- Only request what the app genuinely needs -->

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

<!-- Needed on Android 13+ to show notifications -->
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />

<!-- Camera, location and notification permissions must
     also be requested at runtime from the user. -->

Offline-first design for a field app

1. Save every job update locally first
   (Room database on the device)
2. Mark the record as "pending sync"
3. When network returns, upload in the background
   (WorkManager with a network constraint)
4. On success, mark as "synced"
5. On conflict, server version wins and the
   engineer sees a clear message

Test cases:
[ ] Airplane mode during job close
[ ] Network drops mid-upload
[ ] Phone restarts before sync

import androidx.compose.foundation.layout.Column
import androidx.compose.foundation.layout.padding
import androidx.compose.material3.Card
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Text
import androidx.compose.runtime.Composable
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.dp

@Composable
fun UsageCard(dataLeftGb: Double, daysLeft: Int) {
    Card(modifier = Modifier.padding(16.dp)) {
        Column(modifier = Modifier.padding(16.dp)) {
            Text(
                text = "Data left: $dataLeftGb GB",
                style = MaterialTheme.typography.titleMedium
            )
            Text(text = "Valid for $daysLeft more days")
        }
    }
}

Recharge funnel - events to track

Step                      Event name
1. Open recharge screen   recharge_view
2. Select a pack          pack_selected
3. Tap pay                payment_started
4. Payment success        payment_success
5. Payment failed         payment_failed

Questions the data answers:
- Where do most users drop off?
- Do failures rise on certain devices or networks?

Never log personal data such as full phone numbers
or payment details in analytics events.

Feature Spec
Feature: _______________
User: customer / field engineer / sales staff
Problem it solves: _______________

Screens:
1. _______________
2. _______________

APIs needed: _______________
Offline behaviour: _______________
Analytics events: _______________
Done when: _______________

Android Release Checklist

[ ] Tested on low-end and high-end devices
[ ] Tested on slow and no network
[ ] Runtime permissions explained to users
[ ] No personal data in logs
[ ] Crash-free on internal test track
[ ] Accessibility: text size and contrast checked
[ ] Version code and name updated
[ ] Release notes written in simple language

App Metrics Sheet (weekly)

Metric                       This week   Last week
Recharge success rate        ______      ______
Average screen load time     ______      ______
Crash-free sessions          ______      ______
Support tickets raised       ______      ______

One improvement to try next week:
_______________