如何实现类似Go Keyboard的独立主题应用与主键盘联动功能？

Hey there! Let me break down how you can make your theme apps work seamlessly with your main keyboard app, just like Go Keyboard does. This is all about cross-app communication and data sharing on Android—here’s the step-by-step approach:

The key is to let your theme apps expose their configuration data safely, and have your main keyboard app detect, fetch, and apply those settings. Here’s how to implement each part:

1. Use Content Providers for Safe Cross-App Data Sharing #

Android’s Content Provider is the official, secure way to share data between apps. Your theme apps will host a Content Provider that stores theme details (like background colors, key styles, font paths, preview thumbnails), and your main keyboard app will query this provider to get the theme data.

Example Implementation: #

In your Theme App:

• Define a Content Provider class to expose theme data:

class ThemeContentProvider : ContentProvider() {
    override fun query(
        uri: Uri,
        projection: Array<String>?,
        selection: String?,
        selectionArgs: Array<String>?,
        sortOrder: String?
    ): Cursor? {
        // Access your theme's local database or config file
        val db = context?.openOrCreateDatabase("theme_db", Context.MODE_PRIVATE, null)
        // Return theme configs (e.g., bg_color, key_press_color, preview_image)
        return db?.query("theme_config", projection, selection, selectionArgs, null, null, sortOrder)
    }

    // Implement required methods like onCreate(), insert(), update(), delete() as needed
}

• Register the provider in the theme app’s AndroidManifest.xml, with a custom permission to restrict access to only your main keyboard:

<provider
    android:name=".ThemeContentProvider"
    android:authorities="com.yourthemeapp.neon.theme.provider"
    android:exported="true"
    android:permission="com.yourkeyboard.ACCESS_THEME_DATA" />

<!-- Define the custom permission -->
<permission
    android:name="com.yourkeyboard.ACCESS_THEME_DATA"
    android:protectionLevel="signature" />

In your Main Keyboard App:

• Request the custom permission in its AndroidManifest.xml:

<uses-permission android:name="com.yourkeyboard.ACCESS_THEME_DATA" />

• Query the theme’s Content Provider to fetch and apply settings:

val themeUri = Uri.parse("content://com.yourthemeapp.neon.theme.provider/theme_config")
context.contentResolver.query(themeUri, null, null, null, null)?.use { cursor ->
    if (cursor.moveToFirst()) {
        val bgColor = cursor.getInt(cursor.getColumnIndex("bg_color"))
        val keyPressColor = cursor.getInt(cursor.getColumnIndex("key_press_color"))
        val previewImagePath = cursor.getString(cursor.getColumnIndex("preview_image"))
        
        // Apply these values to your keyboard's UI components
        keyboardView.setBackgroundColor(bgColor)
        keyButtons.forEach { it.setPressedColor(keyPressColor) }
    }
}

2. Use Broadcast Receivers to Notify the Main App of Theme Installs/Switches #

When a user installs a theme app, you want your main keyboard to immediately detect it and add it to the theme list. Use custom broadcasts for this:

Example Implementation: #

In your Theme App:

• Send a broadcast when the theme app is first launched (e.g., in the launcher activity’s onCreate()):

val themeBroadcast = Intent("com.yourkeyboard.ACTION_THEME_AVAILABLE")
themeBroadcast.putExtra("theme_authority", "com.yourthemeapp.neon.theme.provider")
themeBroadcast.putExtra("theme_name", "Neon Glow Theme")
themeBroadcast.putExtra("theme_preview", R.drawable.neon_preview) // Or a content URI

// Restrict broadcast to only your main app
context.sendBroadcast(themeBroadcast, "com.yourkeyboard.RECEIVE_THEME_UPDATES")

In your Main Keyboard App:

• Register a Broadcast Receiver to listen for these updates:

<receiver
    android:name=".ThemeUpdateReceiver"
    android:permission="com.yourkeyboard.RECEIVE_THEME_UPDATES">
    <intent-filter>
        <action android:name="com.yourkeyboard.ACTION_THEME_AVAILABLE" />
    </intent-filter>
</receiver>

• Handle the broadcast to update your theme selection UI:

class ThemeUpdateReceiver : BroadcastReceiver() {
    override fun onReceive(context: Context?, intent: Intent?) {
        intent?.let {
            val themeAuthority = it.getStringExtra("theme_authority")
            val themeName = it.getStringExtra("theme_name")
            val previewResId = it.getIntExtra("theme_preview", 0)
            
            // Add this theme to your main app's theme list
            ThemeManager.addTheme(Theme(themeName, themeAuthority, previewResId))
            // Refresh the theme selection UI
            themeListAdapter.notifyDataSetChanged()
        }
    }
}

3. Handle Theme Uninstalls #

Don’t forget to clean up when a theme app is uninstalled. Register a receiver for the ACTION_PACKAGE_REMOVED broadcast in your main app:

class ThemeUninstallReceiver : BroadcastReceiver() {
    override fun onReceive(context: Context?, intent: Intent?) {
        val packageName = intent?.data?.schemeSpecificPart
        packageName?.let {
            // Remove the theme associated with this package from your list
            ThemeManager.removeThemeByPackage(it)
            // Switch back to default theme if the active theme was uninstalled
            if (ThemeManager.getActiveTheme().packageName == it) {
                ThemeManager.setActiveTheme(DefaultTheme)
                keyboardView.applyDefaultTheme()
            }
        }
    }
}

4. Load Theme Resources Securely #

For assets like background images or custom fonts, avoid file path references (they’ll break if the theme app is uninstalled). Instead:

• Store assets as Base64 strings in the Content Provider (good for small files like icons)
• Use the theme app’s Content Provider to expose asset URIs (e.g., content://com.yourthemeapp.neon.theme.provider/assets/bg.png)
• Bind to a Service in the theme app to stream larger assets directly to the main keyboard

• Use signature-level permissions to ensure only your main keyboard app can access theme data (prevents other apps from interfering)
• Cache theme data locally in the main app to avoid repeated queries to the theme’s Content Provider
• Add a preview screen in the main app that loads the theme’s preview asset before users apply it

内容的提问来源于stack exchange，提问作者Qalb Hussain