You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created, Read, Update, Delete (CRUD) APIs for custom data integration in general is already supported. We just need to research what custom data that these other apps use. Use the debug module to look into the data table and look for custom data mimetypes. Then, create a new custom data module using the existing customdata-x modules as reference. A separate module should be created for each custom data set. E.G. customdata-googlecontacts, customdata-whatsapp
This issue will provide more documentation on how to get started with this work; #17
An issue should be created for each task! Do not use this issue to implement all of the above! This issue is just here as a registry for all custom data from other apps that will be supported for V1.
Note
This work is different from what the native Contacts app is doing. The native Contacts app (or AOSP Contacts) parses a bunch of xml files coming in from other apps that declare their custom data in xml. This allows external apps to show their custom data within the native Contacts app. The native Contacts app does this from an application perspective, which is not the same as what we want to do from a library perspective. We want to provide other developers a concrete way to Create, Read, Update, Delete (CRUD) custom data from other apps. We may still do what the native Contacts app is doing at some point, if we want to provide other developers a way to dynamically integrate custom data from other apps without having to explicitly know about them.
This library should support custom data from;
Created, Read, Update, Delete (CRUD) APIs for custom data integration in general is already supported. We just need to research what custom data that these other apps use. Use the
debug
module to look into the data table and look for custom data mimetypes. Then, create a new custom data module using the existingcustomdata-x
modules as reference. A separate module should be created for each custom data set. E.G.customdata-googlecontacts
,customdata-whatsapp
This issue will provide more documentation on how to get started with this work; #17
An issue should be created for each task! Do not use this issue to implement all of the above! This issue is just here as a registry for all custom data from other apps that will be supported for V1.
Note
This work is different from what the native Contacts app is doing. The native Contacts app (or AOSP Contacts) parses a bunch of xml files coming in from other apps that declare their custom data in xml. This allows external apps to show their custom data within the native Contacts app. The native Contacts app does this from an application perspective, which is not the same as what we want to do from a library perspective. We want to provide other developers a concrete way to Create, Read, Update, Delete (CRUD) custom data from other apps. We may still do what the native Contacts app is doing at some point, if we want to provide other developers a way to dynamically integrate custom data from other apps without having to explicitly know about them.
The work for this is split to #112
The text was updated successfully, but these errors were encountered: