Why I built a real-time announcement system for my app

[@iangrant4756]

That’s such a good idea!

[@shawn.hickman]

Thanks!

[@brendan1]

You mentioned it is displayed when the app is launched. But your video showed it just appearing while not doing anything. You'd have to be careful when the notification appears. I trigger the ratings / review request only when the customer taps on my Tools tab button. What about a notification badge or something and a screen that lists the notifications the user can view if they missed it the first time. They could see a history of those alerts too. It does look pretty though.

[@shawn.hickman]

That’s just how I edited the video. The app only checks for new announcements when coming to the foreground. Otherwise it doesn’t check for any announcements. I have a “What’s New” link in settings that people could use if they missed the announcement message.

[@JungleShrink]

Cool idea! Regarding time sensitive issues like board games, it makes sense why you'd need a server-side system. But for regular app update notifications, why not go with the typical hard coded splash screen with an app version diff variable? Do you find the server side option easier to work with? I've been mulling over various methods of how to serve data to my app for an unreleased project and I'm thinking through the advantages of a server side system for pushing info to users versus having a static file in the app.

[@shawn.hickman]

I've used the app version diff variable approach for a few years now and it's great. The main benefit of a server-side approach for regular app updates is to entice people to update to a newer version of the app. There is a lag-time for people to update apps to the latest version and being able to remotely push a message out could be a nice way to encourage updates. That being said, if you don't have a clear use for the server-side approach right now, then stick with the app-based approach. It's simpler and cheaper.

[@JungleShrink]

@@shawn.hickman yeah, cost is my main concern of trying to implement anything server related. I ain’t exactly making money on my app yet lol.

[@shawn.hickman]

I'd say hold off then. I'm only *just* adding this now and Sofa has been around for a few years.

[@MikaelaCaron]

What do you mean “server side approach” vs “app side?” Like if the announcement is kicked off from the server, or if it’s in an app update?

[@shawn.hickman]

Yea, pushing the announcement info server-side vs embedding the announcement into locally on device for a specific app version

[@PhilipCharron]

Yooooooo! What up? I like how you've contained everything in the JSON file - action text, where the action button goes, etc. Simple and contained. Is the "Ignore" button automatic? If so, what's the thinking behind "Ignore" rather than "OK" or "Dismiss" or "I

[@shawn.hickman]

It's funny you mention the ignore button because after I recorded this video I added a property for controlling the text for that button remotely as well. Sometimes I like using "Ignore" more than "Ok" because it's a clearer, more intentional action. "Ok" can be very vanilla, but "Ignore" has more clarity to it. Just a personal preference. The hard part is figuring out how to work "cereal" into all of this announcements 🤔

[@PhilipCharron]

Makes sense. "OK" doesn't indicate any kind of action, so I can see how "Ignore" gives more context to the action.