Dave PoirierFollowBetter Programming--ListenShareI’ve been working in the software industry for over twenty years, touching all levels of security requirements. Below are my minimum recommendations for all apps:While this list doesn’t fully represent the entire extent of security mechanisms, I find that it covers what I consider the very minimum that every app developer should do.Even if you think the jogging route isn’t critical data, when a celebrity or diplomat enters the jogging route recorded in your app, leaking this data may risk personal harm to the individual.If you have any doubts, play it safe. And remember to do a full threat assessment.12. Use the Swift language for new projects and allocate meaningful resources to your plan to migrate your codebase from Objective C to Swift. Use memory-safe languages for cloud server components.13. Use automated unit tests to ensure your application architecture's designed security elements remain secure as your application evolves.14. Use DocC to document the security features of your application design in the code so that future developers can understand the context and decisions made. This will help prevent security from being accidentally undermined by future changes to the system design.Here’s a reference for more information.For a more complete guide to application security, you should refer to the OWASP MAS by clicking this link.----Better ProgrammingSenior iOS Software Developer at CAEDave PoirierinSwift2Go--2VinitainBetter Programming--37Benoit RuizinBetter Programming--214Dave PoirierinSwift2Go--5Artem Kvasnetskyi--Bhumita Panara--BorisinITNEXT--2İrem ÇelikinInfoSec Write-ups--Meet Patel --Muhammad naufal adli--1HelpStatusAboutCareersBlogPrivacyTermsText to speechTeams