I have made a Parse-based app that allows the user to send a push notification to everyone who downloads the app. It's a kind of quick public address system for a congregation, school, club, etc.
Other leaders have expressed an interest in my app for their communities. But these people are not tech-savvy and have no interest in becoming Apple developers for $100 a year, so building custom apps for them is not an option. Even if I did it for them, I would be concerned that they would mess something up that would require a lot of time on my part to repair. They just want to use the app for their communities.
My question: Could I make custom apps for these groups, keep them on my iTunesConnect account, and simply make a new Parse account for each app? That way, the group leaders would only need to know how to log into Parse and send a push notification on the Parse website.
Thank you,
Eli
You could. It could be done with a single app that everyone downloads and then configures to connect it to their specific parse app.
It's possible that you could write the app so it doesn't know the parse account details and they need to be entered on the device. It's also possible that you could supply that detail with an invite e-mail that opens the app and has the details in the URL query.
Related
I want to send a welcome message to a user that adds my Slack app.
This is considered good practice in the official Slack docs.
What is the right way to implement this?
Should I use the app_home_opened event for that? Is there a built-in mechanism to detect if it was triggered for the first time (because I need to show the onboarding message only once)?
Are there any other events that might be useful for the use case?
Yes. You should use the App Home features on your app. Enabling the app home with some type of instructions or welcome message would be best practice. Along side this, you will subscribe your app to the app_home_opened event type which will let you know whenever a user opens your app's app home. You can then configure your app to respond to these events. Here's a video that might help with this concept.
After #sandra's response and further investigation I would like to share more details on the implementation mechanics:
A user goes through the OAuth process and is then redirected to the app home.
In the application I catch the app_home_opened event.
If the event.tab === 'home' and event.view is not set, it means that the app home is opened for the first time and we need to send the welcome message.
Send user a message (e.g. in the Bolt for JS it's await say('Welcome!')).
Publish the Home view (e.g. in the Bolt for JS it's await client.views.publish(...)).
Useful links:
Official video from Slack about App Home
Official demo app to get some ideal on implementation
Give them a warm welcome on Day 1
Make new hires feel at home with a quick tour of the place. Using integrations like onboarding assistant Greet Bot, you can automate welcome messages and reminders, and share helpful links and documents.
The ideal welcome isn’t only a nice-to-have. It’s a critical early step in the onboarding process that shortens ramp time so your people can get to full productivity fast.
2.Create #new-hires channels
When new folks join, give them a place to find answers to FAQs, access important documents, and meet other new starters. If you’re hiring on a large scale, create multiple channels to bring together all your new hires from specific time periods.
This will boost productivity and can be great for employee engagement. Your new hires will be able to meet their peers and find the essentials fast—not just company policies but recommendations for the best places to grab a bite too.
3.Make sure they hit the ground running
When you need to bring new employees up to speed on a project, one approach is to forward them a load of email threads and wish them luck.
A better way is to invite them to a project channel where they can easily find what they need—pinned posts and files, team members, and conversations—all with a scroll or a search.
4.Help them help themselves
No one wants to feel like a burden when starting a new job. Enable self-service to help new starters get answers for themselves. As an added benefit, it’ll take some heat off your HR team because they won’t have to deal with so many admin requests.
Slack integrates with the apps your people use the most to stay productive and keep on top of HR tasks—apps like Dropbox, Salesforce, G Suite, Workday, Okta, UltiPro, and more.
5.Remind them about the important stuff
You can schedule automated messages to arrive at key times, prompting your new hires to complete the next item on their onboarding checklist. No more missed deadlines, no more time spent chasing people down. Just new employees getting up to full productivity—and full confidence—as quickly as possible.
We've just published our first app in Google Workspace Marketplace (a google docs add-on) and can't figure out how, or if, it is possible to setup an email or other notification (slack notification would be cool) for our Customer Success team to be notified when a user leaves a review of the app.
Appreciate that if we get thousands we will probably turn the notifications off (or filter them in some way), at this early stage though, we're very eager to act on any feedback.
Thanks!
Disclaimer: I am creator of Obsei, and this might be biased answer.
You can try Obsei: an open-source low-code AI powered automation tool.
It can monitor App and Play stores for customer reviews and send notification Slack when someone add review there. Also Obsei can classify review contextually to classify it into issue categories. Refer below image.Obsei workflow
All of these can be achieved free without any cloud hosting requirement. Refer link for more detail.
Happy to answer any queries in this regards.
Working on an application and developing chat integration bot. Note that contrary to some news bots or other tools, there is no central website or server that the bot gets its data from. The software installation comes with a repository, and that is where the bot connects to. Thus, every user, upon installing the software, will basically get their own copy of the bot, alongside with their own repository, etc.
Now, having done that for Telegram: You open the telegram client, initiate a chat with the botfather, get the token for your new bot with one or two commands, and then add that token to my application. Done. Easy for the user to follow, takes a few minutes at most and they have a working bot.
Trying to do the same with Skype, the users must:
Sign up for an Azure account
Provide credit card and phone number verification (that's probably where some users will stop right away)
Log on to the Azure Portal
Create a bot channel, through a myriad of different screens I have to guide the user through.
Have the user obtain the bot's password, again through a variety of different screens he needs to be guided through. (if the user hasn't given up yet, at this point he'll definitely get grumpy)
Enable the Skype channel, and enable the bot to be added to group chats.
Attempt to locate the bot via Skype and eventually add it in.
Now, if I wanted to document this properly, this will be a 10-15 page document with tons of screenshots and all. To do what Telegram does in two minutes or even less. There's so many opportunities in all of this for something to go wrong, that I can't even consider forcing my users to go through this.
Surely, I must be missing something? It can't be that you have to go through this horrible mess of an over-engineering spectacle that is second to none, just to get the most basic bot to function?
All I need is a means to say "this is the bots name, give me its token and API URL so that it can send messages using the REST API". But I can't seem to find this for Skype.
I'd like to know if it's possible to access personal information supplied within an app on a user's device and transmit that information on approach?
Example: Customer has my coffee shop app installed on their device and is logged into their account (where they have provided their first name). As they enter the shop, the barista can see their name on a tablet behind the counter and greet them by their name.
If so, can anyone point me in the direction of a demo or example?
Yes, that is possible, but it has to be done entirely in your app.
app detects the iBeacon
app sends the name (likely entered in the
app settings) to some sort of service (rest api, web service,
etc...)
the app that the barista has access to is notified of the
person approaching.
For a demo app you probably want to look at push notifications really, the iBeacon side is pretty boring for this use case.
As a total aside, make sure this sort of thing is opt-in - this could be creepy, and people don't like creepy.
I want to build something similar to a poll service for mobile but it doesn't need Facebook.
After Facebook's acqusition, is Parse.com still a viable option if your web app does not need Facebook integration? Could app developers (customers) log in to my backend without a Facebook account?
Is it possible to build premium features with Parse and then charge for them?
Do you own your data when using Parse.com? I.e., can you export it in case you decide to move to another service in the future?
I am hoping someone with experience can shed some light on this. Thank you!
After Facebook's acqusition, is Parse.com still a viable option if
your web app does not need Facebook integration? Could app developers
(customers) log in to my backend without a Facebook account?
yes,for now.
Is it possible to build premium features with Parse and then charge
for them?
yes
Do you own your data when using Parse.com? I.e., can you export it in
case you decide to move to another service in the future?
yes
I'd suggest you always have a backup plan,when using a BAAS.I pity Stackmob users that didnt.You dont know if parse will still be there in 3 years or their features and pricing will change.Never rely on a BAAS on the long run.
Yes parse has standalone login features with username, and password, in addition to twitter, and facebook. They even handle lost password reset's via email as long as the user has the email field entered. You can check if the user's email has been verified via the emailVerified field.
I'm using stripe.com's payment system via parse's cloud code. I will admit this is not a complete drop in feature for parse yet, but maybe in the future. stripe is made for developers, and I find it to be a very powerful payment system. I can answer some basic stripe/parse questions as I have written myself basically a semi-complete API for handling customers, card, and charges.