I would like to create a Push To Talk app, in which an account can grant or remove access to be able to talk to. Any device they are signed in with iCloud on are automatically sent the audio files to chat. Audio files are deleted after being listened to or after 4 hours, since this is used as a live voice communication app.
In researching CloudKit, I'm still thoroughly confused on what I can store on the Public Database. If I set up all 'chats' (voice in my case) to have an account GUID associated with them, then they are secured, meaning no one else can change the query to pull or view another accounts information correct? I have heard that if the device is jailbroken, then someone can change the queries, but I'm asking in general, can the Public database on CloudKit be used as a normal database? Or could I at least encrypt the voice data with a key that's stored in the private database and could 'share' the key with the other account I'm wanting to give access to to talk with?
Again to reiterate, I'm also confused how you create the Private Database schema, where the CloudKit Dashboard is only designing the Public correct? Out of all the tutorials I've seen, no one can quite explain if we can use the Public Database the same as any other Cloud Database, since if someone would jailbreak that device, they have the keys to that 3rd party Cloud, the same as CloudKit. There's been a few people ask similar questions (around building a messaging app with CloudKit) but no responses are helpful, some just scream it's public you can't do that, which i don't think is true. Any insight into design wise of the Public Database would be very beneficial. Thanks!