Here's a quick reference list with some common abbreviations that I have came across frequently in my Engineering journey : 1. PR – Pull Request A request submitted by a developer to merge their code changes from one branch to another, typically for review and collaboration before integration. 2. MR – Merge Request Similar to a Pull Request, a Merge Request is used in GitLab to request code merging. It includes review, discussion, and approval before finalizing changes. 3. CR – Change Request A formal proposal to modify a system or product, often triggered by stakeholder feedback, bug reports, or evolving requirements. 4. LADR – Lightweight Architectural Decision Record A brief document that captures an important architectural decision made during a project. 5. BRD – Business Requirement Document Outlines the high-level business needs, objectives, and expectations of a project. It's used as a reference for aligning technical development with business goals. 6. LLD – Low...
Long waiting is over. !! iOS 12 brings Autofill for OTP text field which is close to Android provided a decade back. Previously in iOS we used to toggle between OTP text screen and message inbox. Which was hard to remember and time consuming resulting a bad user experience. Personally, I have been asked from the client/customer couple of times to implement autocompletion for OTP field and took me a lot of time to convey that it is not possible in iOS. Why Autofill was not possible previously? We all know that Apple gives at most care for user privacy. When we see iOS architecture, each individual app is like a separate island. There is no inter-app bridge between apps (exception for Keychain and URLSchemes APIs which gives very limited scope). Thus we cannot read message content from inbox. Where to start Autofilling? First of all, the target SMS need to have the OTP Code with prefix string "Code" or "Passcode"on its message content. Beware of OTP c...