Comparison of architectural patterns of Windows Phone applications

U ovom diplomskom radu su opisani arhitekturni obrasci MVVM, MVP te MVC. Korištenjem navedenih obrazaca implementirane su tri probne, funkcionalno jednake Windows phone aplikacije. Nad spomenutim aplikacijama provedeno je dodavanje novih funkcionalnosti, točnije promijenjen je način spremanja podataka sa lokalne baze na rad sa bazom podataka na poslužitelju. Aplikacija koja je korištena izrađena je na modelu Firma. Aplikacija omogućava unos podataka o partnerima te praćenje njihovog stanja, dodavanje dokumenata te njihovih podstavki itd. Aplikacija je napravljena za Windows phone 7.5 platformu koristeći WindowsPhone SDK7.1 te programski jezik C#. Napravljene aplikacije ukazuju na mogućnost izrade aplikacija sa svim obrascima. Prije same izrade aplikacija, obrazac koji se činio najlakšim za implementirati je bio MVVM. Jedan od glavnih razloga je taj što ga je osmislio Microsoft baš za razvoj aplikacija za WPF, Silverlight pa tako i Windows phone. Razlog usporedbe je bio što su ostali obrasci, naročito MVC, rašireniji od MVVM-a te je puno poznatiji razvojnicima. Iako sam i ja krenuo razvoj sa poznavanjem samo MVC arhitekture nije mi bio problem prebaciti se na druge arhitekture zbog njihove bliskosti, posebice to što dvije od tri komponente su prilično jednake (Model i View). Model je jednak u svim arhitekturama dok je kod View komponente bilo promjena. Razvojem ovih aplikacija sam došao do zaključka da je MVVM dobro zamišljen te da će vrlo vjerojatno biti najbolji obrazac za razvoj kada ga Microsoft još usavrši; točnije kada potpuno prilagodi Windows phone platformu tom obrascu. Povezivanje podataka preko Bindinga je vrlo jednostavno, programski kod koji bi na kraju trebao biti čvrsto razdvojen nije ispao takav zbog mana u platformi. Problemi su nastali prilikom povezivanja komponenti nad kojima nije moguće provesti Binding što će vjerojatno biti popravljeno u novijim verzijama platforme. Onima koji su željni baviti se razvojem Windows phone aplikacija preporučam MVVM obrazac s tim da neće imati problema koji god izaberu.This thesis describes architectural patterns MVVM, MVP and MVC, and then using these patterns I have implemented three functionally equal Windows phone applications. On these three sample applications I have added new funkcionalities, specifically changed the way of saving data from a local database to work with the database on the server. The application was built using the model Firma. The application is used to add, modify and monitor partners and to add their documents and their sub items. The application is designed for the Windows Phone 7.5 platform using WindowsPhone SDK7.1 and the programming language C #. These three applications indicate that it is possible to build applications in all three patterns. Before making the first application, the pattern that seemed the easiest to implement was MVVM. One of the main reasons is that it is designed specifically for Microsoft application development for WPF, Silverlight and Windows phone. The reason for the comparison was that other patterns, especially MVC, are more widespread than MVVM, and are much more familiar to developers. Although I also started the development process with only the knowledge of the MVC architecture pattern it has not been a problem for me. Switch to other architectures was easy because of their similarity, especially that two of the three components are fairly equal, the Model and the View. Model is the same in all architectures while the View component was changed. While developing these applications I have come to the conclusion that the MVVM is well-conceived and will very likely be the best pattern for development when Microsoft improves it. Specifically, when it is fully adapted to the Windows phone platform. Linking data across with binding's makes very simple code that should eventually be firmly separated, but at the end did not turn out like this because of a flaw in the platform. Problems arose when connecting the some components which could not be binded. This problem will probably be fixed in newer versions of the platform. To those who are eager to engage in the development of Windows phone applications I recommend the MVVM pattern