I'm trying to find a design pattern that would best work with the ESRI arcgis runtime environment. From all of the samples I've been looking at, I know they aren't full blow projects, but it's been hard to peg what kind of design patterns they are using. For my own project, I was trying to use a more MVC/MVP approach, but I'm finding it hard to decouple my model being how my model isn't a POJO, but really a wrapper around a graphics layer.
I've been contemplating separating the graphics layer out into a POJO and truly making my model a model, but I'm starting to wonder if that is even an appropriate use of time. I gain unit testability, but I add in considerable amount of bulk (listeners etc.). I realize that might be more of a generic Android problem, but I just didn't know if ESRI recommends a particular design pattern?
Hi Paul,
For recommended design patterns of ArcGIS Runtime Android apps, the maps-app on Github is a great place to start: Esri/maps-app-android · GitHub
There are also some great discussions about design patterns in the guide on developers.arcgis.com:
Design considerations—ArcGIS Runtime SDK for Android | ArcGIS for Developers
I hope these recommendations are helpful.