The document discusses common mistakes made when developing applications using the MVC architecture and coding guidelines for creating APIs. It notes that developers should avoid repeating code, write optimized and readable code that is easy to maintain, and place code in the proper MVC locations such as business logic in the model. The document also provides an overview of the Joomla MVC framework structure and outlines best practices for API coding including limiting code length, avoiding complexity, and not returning full data from the view.

1. Common MistakesCommon Mistakes
MVC ArchitechtureMVC Architechture
MVC Key FeaturesMVC Key Features
MVC Business logicMVC Business logic
Coding Guidlines For API Creation
Joomla MVCJoomla MVC
Coding RequirementsCoding Requirements
API WorkflowAPI Workflow
API RequirementAPI Requirement

2. Common Mistakes
● Avoid MVC architecture in code
● Code redundancy / repetition
● Complex and bulky code writing
● Continuous code
● Forget to write optimise code
● Forget comments

3. MVC Architecture
Controller
View Model

4. Key features
● Business logic
● DRY coding style
● Smart code
● Optimize
● Easy to maintain
● Uniqeness

5. Business logic
● Process of calculating logical process
● Process code
● Execution time
● Optimized code

6. Joomla:MVC frame Structure
● Componenet
- View
- Module
- Helpers
- Includer/libraries
- Tables
● Template

7. Coding Requirements
● Write upto 50-60 line
● Do not write same code in many files.
● If slighty diffrent code, use condition in code avoid
repeatation
● Avoid more complexity
● Make it simple
● Optimize code
● Writen code must be readable

8. ● Place in proper place
- means queries in model
- common function in helpers/includes/libraries
● Avoid to return full data on view.

9. API work flow
App / Site
API Helpers
Models
Libraries
Database

10. API Requirements
● Core functions in use
– Helpers/Libraries/Includes
– Module
– Use controller code if requirement
– Write query to get data

11. Questions....?

12. Thanks