I'm working on a mobile game with increasing daily bonuses based on the number of consecutive days they played (up to 7 days in a row before resetting). I'm looking to increase retention by using push notifications to remind players to log in for their Daily Bonus.
The support staff at our push notification service said this: "This is possible however we don't have any automatic tracking in place for this. It can be done with tags but you will need to add the logic in your app. You could do this by saving the last time the user used your app and then when they come back to your app compare the time. Each time they come back you can just increment your local consecutive days value and then set a tag to match."
If anyone could give advice on how to set this up that would be great. I appreciate the help.
Related
I am using multiple platforms to run a business. I provide 14 tutorial videos to my users after they create an account. What I want is when user sign up, my system should send 1 video / day to that user. Like this
video 1 on day 1
video 2 on day 2
...
...
video 14 on day 14
I want to make a setup in zapier to do that. Zapier should send each video a day unto 14 days a user gets registered.
Can anyone guide me how I can Achieve that target?
It's possible with Zapier, but will use a lot of steps + tasks. You could make a many-stepped zap that is structured like:
New User trigger
Delay until "tomorrow" (Zapier translates this into the correct date at runtime)
Send email w/ video 1
Delay until "2 days"
Send email w/ video 2
etc...
This will work, but probably be too expensive (that's a lot of Zapier tasks). Instead, look into drip email campaigns from any of the popular mail-sending services (such as Mailchimp).
I am working on an mobile app that requires me to change the text displayed either on a weekly or a monthly basis, but I don't want to require the users to have to update the app every day or every week in order to see the changes. I would love suggestions on how to do this.
As a high-level answer, check the device date and display the proper text, if it is fixed and known ahead of time.
If not, have a file or api call send down the information and the next date of when the server should be checked for the next set of data.
I'm getting reports from my app users of many many copies of the same local notification all firing at the same, correct, time and filling the screen with identical copies of the same message. Nothing in the code base has changed. I did see that iOS 10 created additional optional features introduced at WWDC for UILocalNotifications, but I didn't notice any mandatory upgrades. Two questions.
(1) Has anyone else gotten these reports from users?
(2) Any known changes to UILocalNotifications that would require updates to existing code?
I am coding in Xcode 6.1.1 with objective-c.
In my app it is critical that I use the correct time.
I only want the app to use the time of the device when the time is synced with the servers.
If an user is somehow using his/her own "weird" time the app should detect that and tell the user to switch back to use the app.
I know there is NSSystemClockDidChangeNotification, but that only gives back when the time is changed. It does not give back what the change was and if the user switched to "custom" time or synced back to an NTP server.
Question: How do I detect if an user is connected to an NTP server or not?
Maddy is right that you can't specifically find this out from iOS.
However, in the past I've delivered a client for a premium subscription service that had a similar need to know if the user was messing with time. In particular we needed to verify this when there was no network available, in order to prevent the user from accessing premium content after their subscription had lapsed. The very simple mechanism we used was as follows (IIRC):
every time the app launches or comes in from the background, record the current time (eg: in NSUserDefaults)
compare the current time to the last recorded time--if the current time is earlier than the last recorded time, force the user to go online and sign in to the service.
I don't claim it is 100% foolproof, but for our purposes we felt it was good enough to prevent users from trying to circumvent time-based restrictions on accessing premium content.
I have a question which I have not been able to figure out so I decided to see if I can get some help on here.
I am working on an iBeacons project and I have been able to understand the basic function of iBeacons, setting up UUID'S and major and minor id's to specify exact notifications, but my question is how do I dynamically update information I send out to the users without having to go into the code each time to do this. Do I need to create a database to store all my information I want to push out to users? if so how will this database constantly refresh messages pushed out to users? An example would be lets say if you walk into a store and you get a notification in the shoe section saying there is a 10 percent off, you look at the notification but not too impressed and start to walk out, then you get another notification saying for today only you can get a 25 percent off... The app has to dynamically refresh for this to be possible.
Please help me clarify this
Thank you very much for the help
What you probably want is to store this deal information in a web service so you can update it without changing the app. Your app would need to download the updated deal information from the web service either when it starts up or when it sees an iBeacon.
My company, Radius Networks, offers a tool called Proximity Kit that makes this easy. You can assign arbitrary key/value pairs to iBeacons using a web interface. Then your app downloads them automatically an has access to them whenever you see iBeacons.
In your scenario, they key/values could be something like:
primary_offer_text=10% off all shoes
secondary_offer_text=20% off all shoes