“Today is all about Software,” Apple CEO Tim said as he took the stage at WWDC 2018.
It all started with statistics.
- 20 million iOS developers
- 500 million weekly app store visits
- 81% using iOS 11 where only 8% using latest Android
- Developers earned 100 million through App Store
- New iOS 12 will be released as a free update, every model back to the 5S will get a performance boost.
- ARKit, second generation, which included a lot of cool updates, most interesting is the ability for multiple users to observe and interact with the same environment from different angles.
- Apple Screen time, now iOS 12 will tell you how much time you’re spending with your iPhone and which are the apps.
- Do not disturb a lot of improvements, while you are sleeping will hide the notification, one step one time notifications.
- Photos, with iOS 12 they have revamped it. Allowing more search options driven by AI, share the photos through iMessage.
- Siri, it’s handling 10 billion requests per month and now Apple is allowing you to interact with it more, create shortcuts to trigger app features.
- Animojis, more personal now. It’s super accurate, face-tracking and tongue tracking capabilities. Surely it will feel you very familiar.
- Group FaceTime, now chat with 32 people at once with emoji, sticker, and other effects support.
iOS Apps updates
- Stocks, new UI with better performance
- Apple News app.
- Apple iBooks getting a redesign and a new name.
- Voice Memos, iPad getting it for the first time and recording will be now synced to iCloud.
So far biggest functions of the Apple iWatch is fitness, now Apple adding more components which let you challenge your friends.
- Automatic workout detection using your heart-beats(once you stop working out your heart rate decreases, so it will automatically stop).
- Walkie-Talkie, Texting/phone are tough using watch screen so Apple added an instant audio messaging app called walkie-talkie (uses the wifi or cellular to interact with other devices).
- Siri on Watch, allow third-party apps to show you more information. Now just lift your wrist and start talking it means no more “Hey Siri”.
- Podcasts app is coming on your wrist.
SOLID principle is an acronym created by Robert C Martin also unknown as Uncle Bob. It represents five principles for OOPS.
Now the first thought that came to my mind is Why do we need this? Here is the answer, using these principles we can solve the problems of a bad architecture.
Fragility where A small change may break complete module it’s really very difficult to find this if you don’t have good test cases.
Immobility where A component is very hard to reuse in another project or we can say multiple places in the same project because of too many dependencies.
Rigidity where Single change requires lots of developer efforts because it affects several parts of the project.
Here I want to add principles will not turn a bad programmer into a good programmer you need a better judgment there. Principles have to apply with judgment and you must be smart enough to understand when to apply what.
I have also written one blog where they have mentioned one more acronym like SOLID and it’s STUPID. This may hurt your feeling but yes if you are following this you are writing stupid code.
Thank you for reading the quick introduction, In next blogs, I will try to define all principles with Swift Code.
Yesterday, I have posted about How to response Authentication Challange but thoughts came in mind that if you are going with the first options Provide authentication credentials is it really secure and safe? how is client sharing the credentials with the server?
After lots of Google, I have found, how’s NTLM works and it’s pretty interesting to see that client don’t share the password with the server. here are the steps as follow.
- The client makes the request to the server.
- The server needs to validate the user because there is no identity so server generates 16 bytes random number called as the challenge and sends it to the client.
- Client hash this challenge with the user’s password and return it back to the server that is called the response it also includes username as plain text and challenge sent to the client.
- The server sends everything to the domain controller and it uses the username to retrieve the hash of the user’s password from security account manager database and hash the challenge.
- Domain controller shares the response back to the server if they are identical then authentication is successful otherwise a failure.
So the interesting part is here that Network API doesn’t share the password with the server it means it very secure.
Thank you for reading.
Share your thoughts and feeback.