Can I disable specific iOS features with my app? [closed] - ios

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
Is it possible to prevent use of iOS features with my app? For example, preventing use of the camera or prohibiting phone calls or texts during academic class hours.

If the devices are yours, you can enable Guided Access. Then you can prevent the user from leaving the app or doing anything else with it. But if the devices are somebody else's, there's no way for you to put these kinds of restrictions on them from an app.
Apps run inside of a sandbox, where they can only access certain information, and can only do certain things that Apple specifically allows them to do. You can't, for example, prevent normal phone functionality thru your app. You also can't access certain things such as contacts without the user granting permission first, because apps might have legitimate reasons for doing so but shouldn't just be allowed this without the user's consent.
There's really no way to accomplish what you want short of being the supplier of the devices during class. And students could still use their own devices to text and such if they wanted anyway.

Not without jailbreaking. But you can enable Kiosk Mode that doesn't allow leaving a certain app without a password:
Settings -> General -> Accessibility -> Guided Access

No.
iOS does not allow an app to alter any system functionality.

Related

Use of Developer's key for an API [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 8 years ago.
Improve this question
I am new to the shared API technologies. I have noticed, that almost every API has a developer key. For Example, facebook, Google Plus, Googe Maps, Apple iOS, etc...
Well I am not able to understand what is the use of this developers key.? If I am hosting an API how would developers key would benefit me.?
From what I perceived is: The API hosting company is aware of the total transactions from the developers product from which they can charge them.
Is there something more about the developers key.? Does it also maintains the security of the API, if yes, then how.?
A developer key is simply an authentication of who is using the API. If I have an API that I provide to you, and suddenly you start hitting my API with 1000 requests per second, I want an easy way to be able to measure that it is you causing all this load, so I can give you a call and ask you to fix the bug or even revoke your access.
The opposite would be an open API that anyone can hit without credentials. This would limit my options if suddenly bad actors started abusing my API. The only recourse I would have would be to look at what IP address all the requests are coming from, which is a dubious way to identify a consumer of my API. And how would I get ahold of you to ask you to stop?

How do i implement a database for my ios app? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 9 years ago.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Improve this question
So i created my first app which allows users to track there fitness information (workouts, routines, etc). I want take my app to the next step by allowing the user to create there own account and be able to access their workouts from any ios device (all they have to do is log in). I know i have to use databases, but I just don't know where or how to start this process.
Could you recommend any tutorials or perhaps a resource you used to teach yourself? I'm familiar with sql (took a course on it in university.
thanks guys, I apologize for the newb question.
There are many third-party services you can use that can take care of the backend for your app so that you don't need to worry about managing the database yourself. Two of the most popular ones are parse and stackmob. Take a look at their documentations. I personally use parse and would recommend it.
I've never written any os apps, but for applications in general.
There are many ways, one of which is getting a server/website (you can get free ones) and set up the MYSQL database to have the tables you need like users etc.
Then simply send requests via POST/GET to the server which will enter it into the database.Then when they want to login just do the reverse.
I would personally uses sockets, and probably encrypt the data. You may as-well send information such as how long they've used the app for etc.

What is the use of MobileCoreServices/MobileCoreServices.h in iOS [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I have added mobile core services framework many times in my applications but i don't know what is the actual use of this framework.
From apple site i fond only one line explanation:
-------Mobile Core Services Framework-----
The Mobile Core Services framework (MobileCoreServices.framework) defines the low-level types used in uniform type identifiers (UTIs).
For more information about the types defined by this framework, see Uniform Type Identifiers Reference.
So i want to know what type of functionality i can achieve by using this framework.
Please send me the Mobile Core Services Framework use-list.
Regards.......
As described in the answer for a question similar to yours:
The times you need to use UTIs is if you're sharing files between
applications. You'll need to use UTIs to open files downloaded from
Safari or Mail or transferred to the device through iTunes. You'll
also need UTIs if you'd like to send data to another app, like Mail or
to transferred to a computer through iTunes.
And, as Apple describes it, you can use UTI's to describe an entire class of entities with a type (such as the format for files).

Most used iOS versions [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I find it hard to locate some kind of information source which will give me a breakdown of the most used iOS versions as of today. I am working on my app and trying to decide on my "Deployment Target". I want to choose iOS 5.0 but not sure how many iOS 4.x users are out there. Does anyone know of a good place to get this information?
You can have a look here for iOS usage statistics.
As for me, it's ok just concerning about iOS 5, 6 and 7.
Forget about using third party sources for this kind of information.
You only care about marketshare for your specific app which will almost always we wildly different to the global average across all apps.
The only real option is to have some kind of tracking in your app, where it sends the OS version to the server once per week for similar for each user.
For a new app, you should support as many version back as you can with a reasonable amount of development effort. Then use actual statistics gathered from your app to decide when to drop old OS versions.
Accoring to this and this, iOS7 has over 50% usage.

Should HIPAA complinace not allow offline storage in Mobile Native Applications? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Should HIPAA complinace not allow offline storage in Mobile Native Applications??I dont know if already there is this sort of regulation in HIPAA. I assume there is no such thing.
If you feel this question need not be asked in this forum, I request you to completely read this and suggest a programmatic solution for this problem.
Main reason why this came up was that all of the security considerations regarding the Mobile development may be specifically in iOS seems to have been hacked in to once a device is jailbroken or rooted.
I came to know that hardware encryption is hacked.
http://anthonyvance.com/blog/forensics/iphone_encryption/
Then there are questions on iOS 4's encryption techniques.
People claim, Key chain access in iOS can be compromised if the phone is rooted.
Only thing I think which has not met with any skepticism is the sqlCipher.
If you could find any flaws with SqlCipher , please share it.
And I think that, until people find a theft-proof way to manage offline data in Mobile Phones, people can refrain from making offline features for EMR apps where HIPAA compliance is mandatory.
It can be argued that, any system can be hacked when people are desperate to hack it. But I feel Mobile devices can be an easy target. You can lose it as you lose your Handkerchief.
Please share your views.
I agree with bshirley. Your surface of vulnerability is much greater if you are storing many records about many people on the device. But if you are only storing limited info about one person temporarily - as when conducting a query for prescription info or gathering information about a current health problem - then the risk is much lower. Of course you also need to consider whether the hacked phone presents a security risk to the online data, that is, does the app on the phone enable a wrong user to access protected data online?
Here's an application note you may find helpful: "Formotus™ Mobile Solutions and HIPAA Compliance"

Resources