π Iβm currently working as a Technical Lead (Project Management) at Global Dynamic Solutions LLC-United State with full time Remote support & 6Years+ Experienced In Mobile Application Engineering. I'm a passionate & expertise in both native Android development and cross-platform mobile app development using Flutter. With a strong foundation in computer science and years of hands-on experience, I enjoy crafting robust and user-friendly applications that solve real-world problems. I Love to write code & Share Knowledge with my community.
Programming Language: C, C++, JAVA, Kotlin PHP
Development Architecture: MVVM, MVI, MVC
Development Flatform: Android, iOS, Cross (Flutter)
Would be something like that.
<type>(<scope>): <subject>
- build: Build related changes (eg: npm related/ adding external dependencies)
- chore: A code change that external user won't see (eg: change to .gitignore file or .prettierrc file)
- feat: A new feature
- fix: A bug
- docs: Documentation related changes
- refactor: A code that neither fix bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name)
- perf: A code that improves performance
- style: A code that is related to styling
- test: Adding new test or making changes to existing test
- fix: A bug fixing
- config: Project Root Architecture & Design pattern configuration
- use imperative, present tense (eg: use "add" instead of "added" or "adds")
- don't use dot(.) at end
- don't capitalize first letter
- π build
- π chore
- π¦ feat
- π bug
- π docs
- ποΈ refactor
- π perf
- π¨ style
- π§ͺ test
- π¨ fix
- βοΈ Config
π build(app gradle): add new itextpdf library