Ok i'm home.
This is what you are looking at.
I'll ignore the coding side for now and just till you logistics.
"Proceed With Caution App where u can text a scenario and get some advice on how to handle it in a socially "
-You need sms support, root access to whatever the default sms client is on the phone (easier than buliding your own)
-Will the responses be auto-generated or will you have live-response? In the instance of the latter, you will need to set up a response cloud (the word cloud just means outwardly accessible, don't let it scare you. You can do this easily via Azure/AWS/etc
-In order to do that, you will need to purchase a public IP, route it to your sms server (which is what your app will route sms reponses). And that's your cloud right there. You would probably need to ensure that you do not store anything in plain-text because i'm sure there is some legality issue there. In addition to live-reads, you will need to store data so you are looking at database software as WID wont cut it (and doesn't talk to apple devices iirc).
So that's an on-prem sql server or foot the azure/aws (or w/e you prefer) bill and use IAAS. Regardless, find whatever the most cost-efficient way to store your data.
Once messages reach your "cloud", what you do with them is up to you, but i'm assuming the end goal is to provide the curious youngster with a response. To do that, you need to decide what protocol would be best?
Are you going to reply SMS with SMS? I personally would not as I feel that there are some limits on what you can say in a text (character limits, not everyone is using the same phones/os/emojis/etc. But anything else you do would require a frontend (as others have mentioned) and that's more time/cost.
Now notice I haven't said a single word about the actual coding, the difference between the apple platforms and Android, the fact that you will have to continue to update your software or risk being blacklisted when new OS patches come out, and the fact that your app may not be accepted into the Apple eco-system off jump.
I also did not mention anything about the DevOps side. About having an actual devOps team (even if its just 2 guys). Having proper Dev-UAT-Prod.
The reason why I didn't mention these things is because I'm assuming you are not the one building the App. And whoever is actually building the app already knows all of this.
But you would still have to provide the infrastructure on which the code will live. That is not the devs job.
-
You have to customize your cloud and foot the Azure/AWS bill
-
You have to purchase a public IP from your cloud provider
-
You have to purchase a domain and edit the DNS records to point to your public IP
-
You have to decide the limitations of SMS vs HTML etc etc
-
You have to decide if you are going to hire a team to build your front end, and where it will be stored (on your cloud)
-
You have to decide if you are going with a IAAS or building your database
I could go on and on but you get my point.
An app that takes information from a user and gives live information back is an entire engineering process in and of itself that has many moving parts in it.
I remember when I worked for a company that I will not disclose and our CTO came to us and said "Quicken has launched Rocket Mortgage... I need you to build something just as good in 7 months"
That's when I learned that building an app like that.... well.... lets just say we failed
I'm really just scrathing the surface here with all of this. I could type 5 pages on this and not cover a 10th of what you need to know to in order to get started with this. So I implore you to find people who have done it before and put them together with other people who have done it before.
If you have more in-depth questions, PM me