For example, if the initial entry screen in a project is HomeViewController, business logic would be implemented on that screen.
However, if the initial entry screen changes, some logic may need to be moved to the front end.
Initially, I thought it was just a matter of changing the initial home screen, so I proceeded with estimating the development effort, but I realized there were many aspects to consider, so I decided to always consider more when the initial entry home screen changes.
For example, as push notifications and sockets that receive global communication move to the front end, new objects had to be created, and there were many tasks to modify logic that analyzes based on the currently displayed screen.
To implement a feature that saves the screen the user is currently viewing as an image when a button is clicked, follow these steps:
ScreenShot(Save, Share) is well-organized and good for reference in order.
Additionally, can iOS prevent users from capturing the screen?
If a user wants to save a specific screen of the app, they will either record the screen (click screen record) or capture the screen (volume down button + power button).
By default, Apple does not support capture prevention, but it provides capturedDidChangeNotification during screen recording and userDidTakeScreenshotNotification when a screenshot is taken to provide timing.
At that time, you can use methods like UITextField isSecureTextEntry.
Also, libraries are available if you search, so the conclusion is iOS does not officially support capture prevention, but it is possible to implement
.
iOS App Screen Capture/Recording Prevention is a good reference.
I had an interview with a senior developer and talked at a cafe.
We talked about various things, and I organized the memorable parts one by one.