Is it possible to launch and display an app on the Mac login screen? Or add controls to it?
Let's say I want to build a simple mac app that gives the user 3 buttons before logging in. Each button just does some small background thing.
My end goal is to have some way for the user to execute some 'maintenance' tasks without logging in.
Related
I have created Mobile application in React native.
My problem is that whenever i open my app from launcher icon and minimize for sometime (eg: 10 minutes) then if i re-open my application from recent apps or else on clicking launcher icon again it should restart the application as it opening for the first time.
But doesn't matter how much time i minimize the application when i open it again it will open as a previous state.
How to solve this issue.
What Navigation module are you using? Depending on it, you need to call a method to init the app and that method must be called again when you switch back to the app.
Normally, application has their inherent state as snapshot when it go to background if the user do not close directly.
If you are testing on android, pressing backbutton on top of the navigation makes close the application. (you can control this if you want.)
In iOS, pressing home button always send the application into background instead of close.
I am not sure what OS you are using for development. But refer it.
Is there any way by which I can prevent a windows metro app from going to background since it goes in suspended state when in backgroud?
Else how can I show a alert message when I am trying to put app in the background?
Not programmatically: apps cannot override the user's choice here.
Once the app's window is deactivated it is too late for it to show an alert message.
From a system configuration standpoint the Assigned Access feature allows an admin to set up kiosk with a single app which the user can't switch away from.
After choosing the user in the login view, the library saves this information somewhere so that the app has not to ask for the user again.
Where is this information stored? I need to know how to reset this setting for a fresh start?
If you're simply looking to switch between users, there is an easy way to do this when the app starts up.
On iOS, there is a brief message shown at the top of the screen when the app starts up, if you click on that, you can change to a different user.
On Android, there is a notification that you can reach by pulling down from the top of the screen once the app has started. Click on the notification and you can change user.
Is it possible to 'hack' or develop an app that lets you launch an app by pressing an iPhones power button or volume buttons or possibly from the passcode screen?
As an example: pressing the power button 5 times launches the app or sends an emergency SMS. Or entering a certain code into the passcode / lock screen sends an SMS
No. All these features are managed by a different process than your application, and you cannot directly influence that process. You can develop a JailBreak tweak that will allow you to do so, but obviously this is not for Apple AppStore.
What you are asking about is against the Apple Developer TOS. If you do it, you will not pass the App Store Review process and hence will not be able to distribute vie the iTunes App Store. If you don't care about that, then there may be jail break hacks that can help you with that.
I am developing an app that allows the user to make certain changes to tiles on the Windows 8 start screen. When a change has been made within the app, the user will be shown a "View my changes" button. Clicking the button should bring the user back to the start screen.
I have looked into different ways of closing/suspending the app programmatically (and thus taking the user to the start screen), but I have not found a way to achieve this using WinJS. Throwing an exception closes the app, but this seems like a very dirty workaround. Any suggestions?
I'm assuming you are creating secondary tiles and want to show the users what they look like? #mydogisbox is right in that this kind of functionality has probably been deliberatly excluded.
I'd recommend to just do an in-app 'view changes' of whatever changes to secondary tiles the user might have made. In general, I'd argue that this would be a better user experience because you will keep the user engaged within your application and not be essentially kicking them out of the experience.