DEV Community: AbdelHalim Mahmoud

How to write less Boilerplate to make an adapter for simple recycler view

AbdelHalim Mahmoud — Wed, 24 May 2023 18:21:16 +0000

As developers, we know that writing code can be both rewarding and challenging. While creating new features and functionality is exciting, dealing with repetitive and time-consuming tasks can quickly become frustrating. One area where this is particularly true is in writing adapters for simple Recycler Views. But what if there was a way to eliminate this boilerplate code and streamline the process? That's where my new library comes in.

The library is designed to help developers save time and increase productivity by eliminating the need to write boilerplate adapters for simple Recycler Views. With this solution, you can focus on building out more meaningful and impactful features for your application without getting bogged down in repetitive tasks.

But what are some of the specific benefits of using the library? Let's take a look:

Increased Productivity
By removing the need to write boilerplate adapter code, the library helps developers save time and work more efficiently. Rather than spending hours writing and debugging the same code over and over again, you can use the library to generate clean, concise adapters in a fraction of the time.
Reduced Errors
When dealing with repetitive tasks, it's easy to make mistakes or forget important details. This can lead to bugs and issues that are difficult to track down. By using this library, you can minimize the risk of errors and improve the overall quality of your code. The adapters generated by the library have been thoroughly tested and are designed to work seamlessly with Recycler Views, so you can focus on building out your application without worrying about technical details.
Improved Code Readability
Writing clean, readable code is important not just for you, but for other developers who may need to work on your code in the future. By using this library, you can create adapters that are easy to read and understand, even for developers who are new to your codebase. This can be particularly beneficial when working on a team, where clear communication and readability are key.

Getting Started
So how do you get started with this library? It's easy!

Step 1. Add the JitPack repository to your build file

    allprojects {
        repositories {
            ...
            maven { url 'https://jitpack.io' }
        }
    }

Step 2: Add the library dependency

Add the following dependency to your app's build.gradle file:

dependencies {
            implementation 'com.github.abdomi7:BoilrBite:1.0.7'
}

Step 3: Start using BoilrBite

Create an instance of BoilrBite adapter and set it to your RecyclerView:

    val adapter = BoilrBite.createBoilrBiteAdapter(
            items = mutableListOf<DummyModel>(), // List of items to be displayed
            layoutResId = R.layout.item, // Layout resource id
            clickableViewIds = setOf(R.id.btn_dummy, R.id.tv_name, R.id.tv_university), // Set of clickable view ids
            compareItems = { old, new -> old == new }, // Compare items to check for changes
            compareContents = { old, new -> old.id == new.id }, // Compare contents to check for changes
            bind = { view, item -> // Bind the item to the view
                val binding = DataBindingUtil.bind<ItemBinding>(view)
                binding?.tvName?.text = item.name
                binding?.tvUniversity?.text = item.university
            },
            onViewRecycled = { view, item ->
                val binding = DataBindingUtil.getBinding<ItemBinding>(view)
                binding?.unbind()
            })

    binding.rvMain.adapter = adapter // Set the adapter to the RecyclerView

That is it!

Common functions for data manipulation

BoilrBite provides many useful functions for data manipulation:


    adapter.setItems(listOf(DummyModel())) // Set the list of items

    adapter.addOrUpdateItems(listOf(DummyModel())) // Add or update items in the list

    adapter.addOrUpdateItem(DummyModel()) // Add or update a single item in the list

    adapter.clearItems() // Clear all items in the list

    adapter.setSelectedItem(0) // Set the selected item

    adapter.getSelected() // Get the selected item position

    adapter.getSelectedItem() // Get the selected item

    adapter.removeItem(0) // Remove item at index 0

    adapter.removeItems() // Remove items from the list

    adapter.clear() // Clear the list

    adapter.indexOf(DummyModel()) // Get the index of an item

Event Handling

BoilrBite makes event handling easy with the following features:

        adapter.onItemClickListener = object : OnItemClickListener<DummyModel, View?>() {
            override fun onItemClicked(view: View?, item: DummyModel, position: Int) {
                Toast.makeText(this@MainActivity, "Item clicked: $item", Toast.LENGTH_SHORT).show()
            }
        } // Set the item click listener


        adapter.onSelectedItemChange =
            BoilrBite.OnSelectedItemChange<DummyModel> { oldPosition, oldItem, newPosition, newItem ->
                Toast.makeText(
                    this@MainActivity,
                    "new: " + newItem?.id.toString() + "  old: " + oldItem?.id.toString(),
                    Toast.LENGTH_SHORT
                ).show()
            } // Set the selected item change listener

Repo Link: BoilrBite

Conclusion

Overall, using this library to eliminate boilerplate adapter code for simple Recycler Views can help you save time, reduce errors, and improve code readability. If you're tired of writing the same code over and over again and want to focus on more meaningful aspects of your application, consider giving this library a try. I think you'll be pleasantly surprised by how much time and effort it can save you in the long run

How to track phone calls in your app in Android

AbdelHalim Mahmoud — Sun, 14 May 2023 12:18:13 +0000

Phone call tracking is a useful feature that can be added to Android apps for various purposes. With the help of this feature, an app can keep track of different phone call events, such as incoming calls, outgoing calls, missed calls, etc. In this article, we will discuss how you can add phone call tracking functionality to your Android app using the Call Tracker library.

Call Tracker Library Features
The Call Tracker library offers the following features:

Handling different call events, including incoming call received, incoming call ended, incoming call answered, missed call, outgoing call ended, and outgoing call started.
Providing information about each call event, such as the phone number, start time, and end time.

Permissions required

To use the Call Tracker library, you need to include the following permissions in your AndroidManifest.xml file:

    <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
    <uses-permission android:name="android.permission.READ_PHONE_STATE" />
    <uses-permission android:name="android.permission.READ_CALL_LOG" />
    <uses-permission android:name="android.permission.PROCESS_OUTGOING_CALLS" />

Usage

Follow these steps to use the Call Tracker library in your Android app:

Step 1. Add the JitPack repository to your build file

    allprojects {
        repositories {
            ...
            maven { url 'https://jitpack.io' }
        }
    }

Step 2: Add the library dependency

Add the following dependency to your app's build.gradle file:

dependencies {
    implementation 'com.github.abdomi7:call-tracker:1.0.3'
}

Step 3: Extend PhoneCallReceiver

Extend the PhoneCallReceiver class and implement the methods provided for each call event you want to track.

class CallTrackingReceiver : PhoneCallReceiver() {

    override fun onIncomingCallReceived(context: Context, number: String?, start: Date) {
        super.onIncomingCallReceived(context, number, start)
        Log.d("CallRecordReceiver", "onIncomingCallReceived: $number started at $start")
    }

    override fun onIncomingCallEnded(context: Context, number: String?, start: Date, end: Date) {
        super.onIncomingCallEnded(context, number, start, end)
        Log.d("CallRecordReceiver", "onIncomingCallEnded: $number started at $start and ended at $end")
    }

    override fun onIncomingCallAnswered(context: Context, number: String?, start: Date) {
        super.onIncomingCallAnswered(context, number, start)
        Log.d("CallRecordReceiver", "onIncomingCallAnswered: $number started at $start")
    }

    override fun onMissedCall(context: Context, number: String?, start: Date) {
        super.onMissedCall(context, number, start)
        Log.d("CallRecordReceiver", "onMissedCall: $number started at $start")
    }

    override fun onOutgoingCallEnded(context: Context, number: String?, start: Date, end: Date) {
        super.onOutgoingCallEnded(context, number, start, end)
        Log.d("CallRecordReceiver", "onOutgoingCallEnded: $number started at $start and ended at $end")
    }

    override fun onOutgoingCallStarted(context: Context, number: String?, start: Date) {
        super.onOutgoingCallStarted(context, number, start)
        Log.d("CallRecordReceiver", "onOutgoingCallStarted: $number started at $start")
    }

    override fun onReceive(context: Context, intent: Intent) {
        super.onReceive(context, intent)
    }
}

Step 4: Create a foreground service and launch the Call Tracker. For example:

class CallsService : Service() {
    private var record: CallTracker? = null
    override fun onStartCommand(intent: Intent, flags: Int, startId: Int): Int {
        createNotificationChannels()
        record = getInstance()
        record!!.setPhoneCallReceiver(CallTrackingReceiver())
        record!!.startCallTrackingReceiver(this)
        val intent1 = Intent(applicationContext, MainActivity::class.java)
        var pendingIntent: PendingIntent? = null
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
            pendingIntent = PendingIntent.getActivities(applicationContext, 0, arrayOf(intent1), PendingIntent.FLAG_IMMUTABLE)
        }
        val notification = NotificationCompat.Builder(this, CHANNEL_1_ID)
            .setContentText("Service is running")
            .setContentTitle("Service enabled")
            .setSmallIcon(R.mipmap.ic_launcher).setContentIntent(pendingIntent)
        startForeground(100, notification.build())
        return super.onStartCommand(intent, flags, startId)
    }

    override fun onDestroy() {
        super.onDestroy()
        record!!.stopCallTrackingReceiver(this)
    }

    override fun onBind(intent: Intent): IBinder? {
        return null
    }

    private fun createNotificationChannels() {
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            val channel1 = NotificationChannel(
                CHANNEL_1_ID,
                "Channel 1",
                NotificationManager.IMPORTANCE_HIGH
            )
            channel1.description = "This is Channel 1"
            val manager = getSystemService(NotificationManager::class.java)
            manager.createNotificationChannel(channel1)
        }
    }

    companion object {
        const val CHANNEL_1_ID = "channel1"
    }
}

when you want to start the service you can simply call

val startIntent = Intent(this, CallsService::class.java)

startService(startIntent)

Library source code: CallTracker