I'm developing an ToDo app, and I'm planning to use UILocalNotification. I have integrated CoreData with iCloud support.
I have searched a lot on Google how to share the notifications between the devices, but I can't find anything.
So i hope some of you people out there can help a new Swift developere here, so my question is:
1: Can i share notifications between devices without using a server to send push notifications?
2: How many NSLocalnotification can i have on a device?
//Kim
If you are using Core Data with iCloud to keep the data in sync between devices you can somewhat achieve what your after. What you would need to do is detect when new changes are imported from iCloud and refresh the notifications at that point. I have used that approach successfully before but it does come with a few caveats. In particular:
- Without storing additional information the same notification will be shown on multiple devices.
- The synchronising of the notifications is reliant on the iCloud data being updated. This means that without a means to refresh the iCloud data in the background other devices will not be in sync. It may be possible to work around this using an extension or background services but I'm not too familiar with them.
Related
I want to create a social-media website project for my peronsal portfolio. But, I am really confused about how to develop a notification system.
If user-A likes a post of user-B, user-B should be instantly notified. Once he opens it, the notification will be read. Sometimes, even multiple users need to get the same notification. How is this achieved? Not talking about some 3rd-party tool but how the architecture works and if there iss any way to efficiently implement this is Node.js.
I do not want user-B to keep hitting any API for checking. I want the data to come instantly as it does in Facebook, or even in Stack Overflow. Any solution?
I am using MEAN stack.
Does anyone know what events will cause tvOS to purge temp user data on Apple TV? I'm assuming that it will be things like when it needs space to cache movies and other iTunes content. Does this also apply for streaming offline content (i.e. streaming things from local servers in a non-internet connected environment)?
I have a client who wants an Apple TV version of their app. Data is currently stored using CoreData. I will be using CloudKit to sync that data with iCloud. However, the problem is that my client may not have the Apple TV connected to the internet at all times. My concern is if they make a bunch of entries (small data, on the order of a few MBs, max) while the unit is offline. If they never connect the unit to the internet so it can sync with iCloud, is it still possible that OS will purge that use data?
If it still may be purged, what are other options? I know we only get 500kb of NSUserDefaults storage, which is not going to be enough space for my needs.
My assumption is that if the Apple TV is not connect to the internet and not downloading and streaming content from iTunes, the OS will not have a need to purge anything and the user data should be safe.
Can anyone comment on this, or point to some documentation in some magical hidden location on the Apple Developer portal?
I apologize for the question but I don't have the resources to figure it out myself.
I'm looking for features my next iOS / android app should have and as you can imagine, I'm interested on a "pinch of social" that's why getsream seems to be my saver.
After reading the getting started section and the documentation, I found this warning http://getstream.io/docs/#mobile that confuses me.
I supposed getstream is a managed service that takes care of everything letting me use the REST API to build my mobile community within their phones.
Could you please tell me where I'm wrong?
Many thanks
There are two main reasons we do not recommend integrating Getstream client side (i.e. in the browser or on mobile). First, it is hard to guarantee security when you integrate from the client-side, you have to somehow provision tokens for each user's feed (and feeds they want to target with activities http://getstream.io/docs/#targetting), you could also generate an application wide (read/write) token and ship this to all clients but this is also a bad idea for obvious reasons. Second, we do not recommend using Getstream to store all your activity data, you store references to objects in your local database and enrich the activities from getstream at read time (have a look at our integration libraries for Django/Rails).
I'm new to Azure Mobile Services as well as mobile development.
From my experience in web development, retrieving data from the database is done part by part as the user requests more data i.e. the website doesn't load all the data on one go.
I'm implementing this principle in mobile app wherein data is loaded (if already in the local db) or downloaded (if not yet in the local db) as the user scrolls down.
I'm using Azure Mobile Services Sync Table to handle the loading of data in the app. However, i wont be able to paginate the downloading of data. According to this post, the PullAsync method downloads all data that has changed/added since its last sync and doesn't allow for using take/skip methods. This is because PullAsync uses incremental sync.
This would mean there will be a large download of data during the first ever launch of the app or if the app hasn't been online for a while even if the user hasn't requested for the said data (i.e. scrolled to it).
Is this a good way for handling data in mobile apps? I like using SyncTable cos it handles quite a lot of important data upload/download stuff e.g. data upload queuing, download/upload of data changes. I'm just concerned with downloading data that the user doesn't need yet.
Or maybe there's something i can do to limit the items PullAsync downloads? (aside from deleted = false and UserId = current user's UserId)
Currently, i limited the times PullAsync is called to the Loading Screen after the user logs in and when the user pulls to refresh.
Mobile development is very different from web development. While loading lots of data to a stateless web page is a bad thing, loading the same data to a mobile app might actually be a good thing. It can help app performance and usability.
The main purpose of using something like the offline data storage is for occasionally disconnected scenarios. There are always architectural tradeoffs that have to be considered. "How much is too much" is one of those tradeoffs. How many roundtrips to the server is too much? How much data transfer is too much? Can you find the right balance of the data that you pass to the mobile device? Mobile applications that are "chatty" with the servers can become unusable when the carrier signal is lost.
In your question, you suggest "maybe there's something i can do to limit the items PullAsync downloads". In order to avoid the large download, it may make sense for you to design your application to allow the user to set criteria for download. If UserId doesn't make sense, maybe a Service Date or a number of days forward or back in the schedule. Finding the right "partition" of data to load to the device will be a key consideration for usability of your app...both online and offline.
There is no one right answer for your solution. However, key considerations should be bandwidth, data plan limits, carrier coverage and user experience both connected and disconnected. Remember...your mobile app is "stateful" and you aren't limited to round-trips to the server for data. This means you have a bit of latitude to do things you wouldn't on a web page.
We are creating our first google glass app and I had some security questions that came up that I can't seem to find a definitive answer to on the web. They are as follows:
What apps are available for us to be able to wipe the glass (factory reset) remotely if they are ever misplaced or lost?
Is there an app or a way to automatically wipe the glass maybe at a certain time everyday of the data that is one them?
When we do a factory reset, is the data securely wiped from the device? Or like a PC is the data still there for possible usage if the device memory is hacked into directly?
If we pass data over the network, is it passed using some sort of encryption currently? Or do we have to take this into account when developing our app?
Is there a way to allow multiple people to use the device without having to wipe the device and setup with another account? The only way we were able to login using 2 different accounts was for the first person to factory reset it and allow the next person to login using their account. What we were envisioning was a way for the device to securely authenticate and allow multiple users to use it differently somehow without having to reset it.
The only current way to lock the device that I found is to create the swipe/tap pattern that is included. Are there any apps that allow for a more secure type of login?
If anyone can help on any of the questions, that would help out a lot.
Thanks!
The MyGlass webapp and mobile app allow you to do a remote device reset. From the mobile app, you can go to Settings while the webapp does it from the MyGlass -> Device Info page.
There is no way to do an automatic reset every day that I'm aware of. What are you trying to do here? Just reset it to a known state every day for development?
At this time, you probably can't count on it being a secure reset.
This is a pretty vague question. Google hasn't provided details on the sharing protocol, but it is a safe bet that this is done using SSL on some level. From their servers to yours using the Mirror API must be done using HTTPS. Of course, if you're doing the network data passing yourself, then it's up to you.
No, this isn't possible at this time. Glass is a very personal device. More so than phones, and most phones don't have a profile feature!
I'm not aware of any, but I'm not sure how much more secure you can get and still be usable. Can you elaborate on what you're envisioning?