# mvc MVC (Model-View-Controller) is a software architectural pattern that separates an application into models, views, and controllers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Android Architecture Patterns: A Comprehensive Pre-Interview Guide DevFeed: [Android Architecture Patterns: A Comprehensive Pre-Interview Guide]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2025-03-18T20:01:26Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Android](), [Architecture & Design](), [mvc](), [Mobile](), [Jetpack Compose]() Tags: [android](), [android-architecture](), [architecture](), [code](), [comparisons](), [examples](), [guide](), [interview](), [mvc](), [patterns]() ### AI overview A pre-interview guide to Android architecture patterns. It explains why architectural patterns matter and covers MVC, MVP, MVVM, MVI, and modern Jetpack Compose implementations, with code examples and comparisons. ### Source excerpt Looking to brush up on Android architecture patterns before your next mobile interview? This guide covers everything from traditional MVC to modern Jetpack Compose implementations, with code examples and comparisons of MVC, MVP, MVVM, and MVI patterns. ## Replace Useless Cases with Interfaces DevFeed: [Replace Useless Cases with Interfaces]() Original publisher: [Read original article]() Published: 2024-08-15T00:00:00Z Content type: article Language: en Sources: [Donovan LaDuke - Developer]() Topics: [Code](), [mvc](), [Framework]() Tags: [architecture](), [class](), [dependencies](), [function](), [implement](), [interface](), [interfaces]() ### AI overview The article presents an alternative to dedicated pass-through use-case classes: define use-case interfaces and implement them directly in the repository. This preserves architectural benefits while reducing unnecessary code. It also discusses using invoke-operator extensions and the resulting trade-off of exposing an additional function. ### Source excerpt An alternative approach to avoiding Useless Cases by making Use Case interfaces without dedicated Use Case classes ## Graphical Applications in Haskell with MVC and Gloss DevFeed: [Graphical Applications in Haskell with MVC and Gloss]() Original publisher: [Read original article]() Published: 2022-06-27T00:00:00Z Content type: tutorial Language: en Sources: [Romes' Musings]() Topics: [mvc](), [Functional programming](), [Haskell](), [Graphics](), [Library](), [User Interfaces](), [Simulation]() Tags: [functional-programming](), [graphics](), [haskell](), [library](), [mvc](), [simulation](), [user-interfaces]() ### AI overview This article explains the model-view-controller pattern and how it maps to functional programming in Haskell. It uses the Gloss library to build a graphical application and illustrate the model, view, and event-handling components with a simple employee simulation. ### Source excerpt Contents 1 MVC 2 Functional MVC: Gloss 2.1 Picture 2.2 Event 2.3 Gloss 1 MVC Model-view-controller (MVC) is a software architectural pattern commonly used for developing user interfaces that divide the related program logic into three interconnected elements. MVC says that an interactive application should consist roughly of three main parts - Model, View, and Controller. The Model is the data and state that we need to keep track of to model our application. If you're programming a Chess game, the model could consist of the state of the board (which pieces are where), the time passed since the last player played, whose turn it is, etc... The View is the definition of how our model should be displayed to the user. Intuitively, you can think of it as a function Model -> UI (and begin to see how functional MVC might be interesting). For the above example, the view would define how the chess board can be shown to the user (a 3d object, a 2d ascii board, ...), where the time passed shows up in the screen, etc. The Controller handles all events and interactions with the application and how they modify the existing model. In chess, the controller could define that when a player drags a piece in the board, the position of that piece in the board model changes to the new position, the current turn changes to the other player, and the time passed is reset to zero. And the three relate in the following manner: MVC diagram from Wikipedia 2 Functional MVC: Gloss How does the model-view-controller idea translate into functional programming? It turns out to be quite simple because the three parts match basic FP concepts. We'll focus on the library Gloss to develop a graphical application. Gloss is very easy to setup, provides abstractions for drawing graphics, and outlines the MVC compoonents clearly. We'll implement a simple simulation of the 101companies employees to illustrate the concepts. To define the model, the structure which is updated thorought the program, we simply define ## Why Businesses Use the Zend Framework DevFeed: [Why Businesses Use the Zend Framework]() Original publisher: [Read original article]() Author: Neeraj Khosla Published: 2022-05-17T08:30:36Z Content type: article Language: en Sources: [Our Latest Backend Development Insights]() Topics: [PHP](), [Framework](), [Application Development](), [web applications](), [mvc](), [Encryption](), [Open Source](), [Testing]() Tags: [application-development](), [backend-development](), [encryption](), [framework](), [libraries](), [mvc](), [open-source](), [php](), [testing](), [web-applications](), [zend-application-development](), [zend-framework](), [zend-framework-development-services-in-toronto]() ### AI overview This article explains why businesses use the Zend Framework, now known as Laminas, for PHP web application development. It describes its MVC support, encryption, database support, libraries, integration, rapid development features, testing components, and maintenance benefits. ### Source excerpt Statista's reports say that PHP is the most popular language contributing to 45.43% of the market. PHP is ruling the web and computer technology all over the world. However, with the vast array of frameworks available, businesses only choose the best and the most suitable ones. Zend Framework has more than 570 million installations. Zend ... WHY DO BUSINESSES POPULARLY USE THE ZEND FRAMEWORK? Read More " The post WHY DO BUSINESSES POPULARLY USE THE ZEND FRAMEWORK? appeared first on Orion. ## Using GraphQL with Ruby on Rails DevFeed: [Using GraphQL with Ruby on Rails]() Original publisher: [Read original article]() Author: Erin Fox Published: 2021-11-18T11:00:05Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Ruby on Rails](), [Ruby](), [mvc](), [API](), [Framework](), [web applications](), [Programming language](), [Front end](), [React]() Tags: [api](), [apis](), [apollo](), [applications](), [architecture](), [backend](), [business-logic](), [community](), [declarative](), [framework](), [frontend](), [graphql](), [how-to](), [mvc](), [programming](), [rails](), [react](), [ruby](), [ruby-on-rails](), [ruby-programming-language](), [web-applications]() ### AI overview A tutorial introducing Ruby on Rails and GraphQL, then demonstrating how to build and query a Rails-GraphQL API with React and Apollo. ### Source excerpt Objective: Learn how to create a new project with Ruby on Rails and GraphQL while setting it up to use React and Apollo. The focus is on getting the API running and executing a query. Introduction Ruby on Rails is an MVC (model, view, controller) framework that you can use to build web applications using the Ruby programming language. GraphQL is a declarative query language and server-side runtime that makes it easier for frontend developers to perform data fetching. ## Converting a Laravel App to a Shopify App DevFeed: [Converting a Laravel App to a Shopify App]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2021-08-27T14:11:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Laravel](), [Shopify](), [web applications](), [PHP](), [mvc](), [Composer]() Tags: [applications](), [ecommerce](), [framework](), [laravel](), [mvc](), [php](), [shopify](), [tutorial]() ### AI overview A tutorial explaining how to build a private or custom Shopify app with Laravel. It covers creating the app in the Shopify Dashboard, configuring callback and redirect URLs, adding Shopify support to Laravel, installing the osiset Shopify component, and setting credentials and API scopes. ### Source excerpt This blog post tackles the odd topic of taking a Laravel application and converting it to a Shopify app. Overview Shopify is an ecommerce platform for building hosted shopping sites. With Shopify your whole ecommerce experience exists on a shopify url (whether the domain is .shopify.com or not; Shopify is serving everything and the underlying source of data is Shopify itself). Laravel is an MVC based framework for building web applications using the php language. In this blog post, I will attempt to document all the steps to build a "shopify app" using Laravel. A Shopify app is a web application which, can be hosted anywhere, that authenticates itself to Shopify and is embedded in a page on the Shopify website. Step 1: Create a Shopify App Using the Shopify Dashboard There are a few different types of Shopify apps: Private / Custom - A private app can only be used by one shopify site and cannot be listed in the Shopify app catalog. Private apps have no review / approval cycle. Public - A public app is listed in the Shopify catalog, is reviewed and approved by Shopify In this tutorial we will be focused on private / custom apps. The first step is to create our app. This can be done with this url: https://partners.shopify.com/ There are two url settings: The Callback url; this might also be called the App url (Shopify has changed their UI a number of times) The Redirect uri; this might be called the "Allowed redirection URL(s)" The callback url needs to be set to your home route, the default route for your application. The redirect uri needs to be set to the /authenticate route (this is automatically provided by ) Note: Everything you do with the Shopify website needs to be done in Chrome. No other browser such as Brave seems to work. Step 2: Adding Shopify Support to Your Laravel App The first step is to install the osiset shopify component: composer require osiset/laravel-shopify After that you need to generate a configuration file: php artisan vendor:publish --tag= ## Announcing CodeRAD 2.0 Preview DevFeed: [Announcing CodeRAD 2.0 Preview]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2021-08-13T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Framework](), [mvc](), [Java](), [Kotlin](), [Mobile](), [User Interfaces](), [Developer experience]() Tags: [announce](), [declarative](), [developer-experience](), [feature](), [framework](), [java](), [kotlin](), [mobile](), [mvc](), [native](), [performance](), [preview](), [productivity](), [real-time](), [user-interfaces](), [view](), [xml]() ### AI overview CodeRAD 2.0 is announced as a developer preview of an MVC framework for building native, mobile-first applications in Java and Kotlin. The release adds XML-based declarative views, property binding, and a simulator-based pseudo-hot-reload workflow with a stated 1-2 second update delay. ### Source excerpt We are proud to announce the immediate availability of the CodeRAD 2.0 developer preview. CodeRAD is a modern MVC framework for building truly native, mobile-first, pixel-perfect applications in Java and Kotlin. ## Battle-tested template project for backend with Kotlin and Ktor DevFeed: [Battle-tested template project for backend with Kotlin and Ktor]() Original publisher: [Read original article]() Author: Yev Kanivets Published: 2021-07-16T05:24:17Z Content type: tutorial Language: en Sources: [xorum.io - Medium]() Topics: [Kotlin](), [Ktor](), [Template](), [mvc](), [Authentication](), [Authorization](), [Framework](), [API](), [Firebase](), [Gradle](), [Heroku](), [Postman]() Tags: [api](), [architecture](), [authentication](), [authorization](), [backend](), [firebase](), [gradle](), [heroku](), [intellij](), [intellij-idea](), [kotlin](), [ktor](), [mvc](), [open-source](), [postgresql](), [postman](), [project]() ### AI overview This article presents a personal Ktor template for Kotlin backend applications, describing its production use, project structure, tools, libraries, MVC-based architecture, API design, Heroku deployment files, and Firebase Auth integration. ### Source excerpt With Kotlin and Ktor technologies gaining more popularity among the community of backend developers, dozens of different sample applications and templates are created and published as open-source projects. Ktor is an asynchronous framework for creating microservices, web applications, and more. It's fun, free, and open source. So it doesn't force any particular architecture, set of libraries, or framework to be used, which means that you are free to choose what's best for you and your project. Today, I'm finally ready to share my personal Ktor template, polished by almost a year of use in production applications. This article gives a short overview of the template, its architecture, chosen tools, and libraries. Tools Since we are using Kotlin to develop Ktor applications, pretty much any IDE compatible with Java/Kotlin should work. But the default choice is IntelliJ IDEA, of course. Community edition (free) will work just fine. Postman is a great choice for documenting, testing, and sharing your backend APIs. There are many similar tools. You can use cURL requests, for example. But always think about your API users first. What will be the most convenient for them, as they depend on you a lot. Structure Most of the Kotlin projects (including Ktor) are powered by Gradle, so they look quite similar. My template isn't different, with many Gradle-related files in the root and single src folder. Other files are related to Heroku deployment, but more on this later. Architecture Ktor isn't forcing you for any particular approach, so you are free to choose and implement the architecture that fits your needs best. In our case, we implemented classical MVC (Model -- View -- Controller) architecture with a public API instead of View and dedicated Interactors, which encapsulate all business logic related to each endpoint. Firebase Auth Most applications require some authentication and authorization business logic, so my template includes one of the possible implementations out of ## A Simple Laravel Hello World DevFeed: [A Simple Laravel Hello World]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2021-05-27T13:02:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Laravel](), [Composer](), [mvc](), [HTML](), [Rails]() Tags: [how-to](), [laravel](), [make](), [mvc](), [php](), [route](), [view]() ### AI overview A step-by-step Laravel tutorial that builds a minimal Hello World application using Composer, a controller, a route, a variable, and an HTML view. It explains that the example demonstrates parts of an MVC framework without covering models or database connectivity. ### Source excerpt As of late I've been working in Laravel and figuring out how Laravel differs from Rails. And while I have a bigger blog post in the works, I thought there was learning value in a simple Hello World implemented in Laravel. Hello World is a simple program that just puts Hello World on the screen. Here's how I thought a Laravel version of this should work: Be a whole Laravel application Be a single controller Be a single route Define the text "Hello World" as a variable, $text, in the controller Display that on the screen via an HTML template While this doesn't illustrated models and database connectivity, this actually illustrates how to use a surprising amount of an overall MVC framework. Step 1: Creating an Application The first step is to use composer to generate the overall application with: composer create-project laravel/laravel hello_world The next step is to change into the directory with: cd hello_world and then open the code base with: mate . or if you use Sublime: subl . Step 2: Generating a Controller Back at your command line, you want to generate a controller with: php artisan make:controller HelloController This will create a file named HelloController in app/http/Controllers: ls -l app/Http/Controllers total 16 -rw-r--r-- 1 sjohnson staff 361 May 18 11:37 Controller.php -rw-r--r-- 1 sjohnson staff 122 May 27 09:12 HelloController.php Inside the controller you want to add the following code (some of which will already be there from the generator): public function index() { return view('hello_index'); } inside the "class HelloController extends Controller" block of code (it goes inside the {} braces). Step 3: Adding a Route Moving back to the code base, you want to edit the file routes/web.php and add this line: Route::get('/hello', 'App\Http\Controllers\HelloController@index'); This adds a single route, /hello, which is then handled by the Hello controller and the hello_index action. You can test that this route is available by running: php artisan rout ## RAD Chat Room - Part 5 DevFeed: [RAD Chat Room - Part 5]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2020-05-28T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Tutorial](), [Messaging](), [ui](), [mvc](), [Back end](), [webcam](), [WebSocket]() Tags: [architecture](), [back-end](), [camera](), [capture](), [library](), [messaging](), [mvc](), [tutorial]() ### AI overview Part 5 of a RAD Chatroom tutorial adds a capturePhoto action that lets users select or take an image and insert it into a chat message. It also explains that the mock application has no server integration and recommends the cn1-websockets library as a starting point. ### Source excerpt This is part 5 of the RAD Chatroom tutorial. You can find part 1 here, part 2 here, part 3 here and part 4 here. Adding A Photo Capture Feature Most messaging applications include the ability to add photos to messages. Let's add this feature to our chat app now. First we'll define a new action called "capturePhoto", and add to the TEXT_ACTIONS category of our view node. public static final ActionNode capturePhoto = action( icon(FontImage.MATERIAL_CAMERA) ); ... ViewNode viewNode = new ViewNode( actions(ChatRoomView.SEND_ACTION, send), actions(ProfileAvatarView.PROFILE_AVATAR_CLICKED_MENU, phone, videoConference), actions(ChatBubbleView.CHAT_BUBBLE_LONG_PRESS_MENU, likeAction), actions(ChatBubbleView.CHAT_BUBBLE_BADGES, likedBadge), actions(ChatRoomView.TEXT_ACTIONS, capturePhoto) __**(1)** ); __1 Added capturePhoto action to the TEXT_ACTIONS category so that it will appear as a button beside the text field. And we'll also add a handler for this action, which will capture a photo, and embed the photo in a message that we will add to the chat room's view model. ## RAD Chat Room - Part 1 DevFeed: [RAD Chat Room - Part 1]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2020-04-30T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Tutorial](), [App](), [mvc](), [ide](), [Code]() Tags: [app](), [ide](), [mvc](), [project](), [tutorial]() ### AI overview A step-by-step tutorial on using the RADChatRoom library and CodeRAD in a Codename One application. It introduces the ChatRoomView component, explains the MVC-based setup, and covers project creation, CSS activation, and dependency installation. ### Source excerpt This tutorial describes how to use the RADChatRoom library to quickly and easily add a nice-looking, fully functional chat room to your Codename One application. This is part 1 of a multi-part series of posts over the next few weeks. The finished product will look like the following: You can download the full source of this tutorial's project here. You can also try it out yourself here. ## Managing Massive View Controllers in iOS MVC Applications DevFeed: [Managing Massive View Controllers in iOS MVC Applications]() Original publisher: [Read original article]() Published: 2020-02-20T18:00:00Z Content type: opinion Language: en Sources: [Rambo Codes]() Topics: [mvc](), [iOS](), [iOS development](), [SwiftUI](), [Testing]() Tags: [app-architecture](), [apple](), [ios](), [ios-development](), [mvc](), [swiftui](), [testing](), [unit-tests]() ### AI overview The article discusses problems that arise when iOS MVC applications develop massive view controllers, tightly coupled screens, and difficult-to-write unit tests. It considers how to split view controllers while supporting older iOS versions and UIKit alongside SwiftUI. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## Choosing an Architecture Pattern for Android Applications DevFeed: [Choosing an Architecture Pattern for Android Applications]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2019-08-16T00:00:00Z Content type: tutorial Language: en Sources: [Android Essence]() Topics: [Android](), [mvc](), [App](), [Code]() Tags: [android](), [architecture](), [architecture-pattern](), [mvc](), [mvi](), [mvvm](), [patterns]() ### AI overview This tutorial explains why Android applications need architecture patterns and compares approaches including MVC, MVP, MVVM, MVI, and MVU. It emphasizes separating application code into distinct components rather than placing all code in an Activity. ### Source excerpt As an Android developer, one of the questions I constantly see asked within the community is "what architecture pattern should I use?" This discussion usually leads to a handful of buzzwordy acronyms: MVC MVP MVVM MVI MVU?? (We don't talk about this but apparently it's the new kid on the block) This can be really intimidating to new Android devs, as well as seasoned veterans who are constantly questioning if they're using the right one. Whether you're trying to decide which one to learn, or wondering if the one you already use is best for you, this post will help lead you to the right decision. ## The next CEO of Stack Overflow DevFeed: [The next CEO of Stack Overflow]() Original publisher: [Read original article]() Author: Joel Spolsky Published: 2019-03-28T14:00:53Z Content type: news Language: en Sources: [Joel Spolsky]() Topics: [Stack Overflow](), [Microsoft](), [Software as a service](), [ASP.NET](), [mvc](), [.NET]() Tags: [advertising](), [asp-net](), [browser](), [ceo](), [co-founder](), [employees](), [microsoft](), [mvc](), [net](), [news](), [revenue](), [saas](), [software](), [stack-overflow]() ### AI overview Joel Spolsky announces that Stack Overflow is looking for a new CEO. He is stepping away from day-to-day operations to become chairman of the board, while describing the company's growth, profitability, products, employees, and audience. ### Source excerpt We're looking for a new CEO for Stack Overflow. I'm stepping out of the day-to-day and up to the role of Chairman of the Board. Read more "The next CEO of Stack Overflow" ## Breaking The Buzzwords Barrier Part 3: ViewModel DevFeed: [Breaking The Buzzwords Barrier Part 3: ViewModel]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2018-06-01T00:00:00Z Content type: tutorial Language: en Sources: [Android Essence]() Topics: [mvc](), [Android]() Tags: [android](), [architecture-components](), [lifecycle](), [mvvm](), [rotation](), [viewmodel]() ### AI overview This tutorial explains the difference between the ViewModel concept in MVVM architecture and Android's lifecycle-conscious ViewModel class. It describes how Android Architecture Components retain ViewModel data across configuration changes such as rotation. ### Source excerpt So far we've covered four big buzzwords used in our application: Model-View-ViewModel Room RxJava Repository Pattern Now, we should circle back to the beginning. Following our diagram outlined in the previous parts, the next component we can begin to work on is our AccountViewModel: Naturally, this may bring up some confusion. We already discussed ViewModels in part 1. Well, depending on context, we may not be referring to the same thing. ## Accelerating Android Talent Through Community Bootcamps DevFeed: [Accelerating Android Talent Through Community Bootcamps]() Original publisher: [Read original article]() Author: Julia Hurrelmann Published: 2018-02-27T22:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Android](), [Shopify](), [coding-community](), [software-development](), [mvc](), [JSON]() Tags: [android](), [community](), [developer](), [development](), [json](), [mvc](), [shopify](), [skills](), [software-development]() ### AI overview Shopify describes an Android Bootcamp designed to help developers transition into mobile development through a two-day workshop. Participants build a simple quiz app while learning Android views with XML, lifecycles, MVC, JSON parsing, libraries, and remote data retrieval. ### Source excerpt 6 minute read The mobile team knew they needed developers, particularly Android developers. A few years ago, Shopify pivoted to mobile-first, which led to the launches of Shopify Mobile, Shopify Pay, Frenzy, and others. To maintain momentum, Shopify had to keep building up its mobile talent. Back when Shopify's mobile teams spun up, many of our then-early mobile developers never did any mobile development before, instead teaching themselves how to do it on the job. From this observation, we had an insight: what if we could teach developers how to build an Android app, via a Shopify-hosted workshop? The benefits were obvious: this educational initiative could help our local developer community pick up some new skills, while potentially allowing us to meet exciting new talent. The idea for Android Bootcamp was born. ## Reactive Apps with Model-View-Intent - Part 1: Model DevFeed: [Reactive Apps with Model-View-Intent - Part 1: Model]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2017-01-09T09:00:00Z Content type: tutorial Language: en Sources: [Hannes Dorfmann]() Topics: [RxJava](), [android-development](), [reactive](), [mvc]() Tags: [android-development](), [immutability](), [mvc](), [mvi](), [mvvm](), [patterns](), [process](), [reactive](), [rxjava]() ### AI overview This first part of a blog series explains why a well-defined Model matters in Android applications using Reactive Apps, RxJava, and Model-View-Intent (MVI). It contrasts this approach with MVC, MVP, and MVVM, and connects a Model to issues such as state, configuration changes, navigation, process death, and immutability. ### Source excerpt Once I have figured out that I have modeled my Model classes wrong all the time, a lot of issues and headache I previously had with some Android platform related topics are gone. Moreover, finally I was able to build Reactive Apps using RxJava and Model-View-Intent (MVI) as I never was able before although the apps I have built so far are reactive too but not on the same level of reactiveness as I'm going to describe in this blog post series. ## MVVM-C A simple way to navigate DevFeed: [MVVM-C A simple way to navigate]() Original publisher: [Read original article]() Author: Susann Proszak Follow Published: 2016-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [iOS development](), [mvc](), [Mobile](), [navigation](), [reusable code]() Tags: [architectures](), [business-logic](), [design-patterns](), [ios-development](), [mobile](), [mvc](), [mvvm](), [navigation](), [reusable-code](), [testing]() ### AI overview An introduction to the MVVM-C design pattern for iOS development. The article explains how coordinators handle application navigation and flow while view models contain business logic, using a small demo app to illustrate the approach. ### Source excerpt When thinking about design patterns and architectures in iOS development, MVC might be the first thing that comes to mind for most of you. But throughout the last years, MVC got a really bad reputation. Probably a lot of you heard about MVC as the massive view controller. ## Android Software Architecutre by Example DevFeed: [Android Software Architecutre by Example]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2016-06-02T00:00:00Z Content type: comparison Language: en Sources: [Hannes Dorfmann]() Topics: [Android](), [flux](), [mvc](), [Redux](), [Open Source]() Tags: [android](), [flux](), [mvc](), [open-source](), [redux](), [video]() ### AI overview A video presentation comparing MVC, MVP, MVVM, Redux, Flux, and MVI architectural patterns and their application to existing open-source Android applications. ### Source excerpt Comparing some architectural design patterns like MVC, MVP, MVVM, Redux, Flux, MVI and how they could be applied on existing open source applications. ## Presenters don't need lifecycle events DevFeed: [Presenters don't need lifecycle events]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2016-03-24T09:00:00Z Content type: opinion Language: en Sources: [Hannes Dorfmann]() Topics: [mvc](), [Library](), [Code]() Tags: [code](), [components](), [library]() ### AI overview The article argues that MVP Presenters in Mosby do not need Android lifecycle callback methods. It says Presenters should coordinate the view, transform model data for presentation, and bridge to business logic, while only tracking whether a view is attached. It discusses LightCycle as a way to delegate lifecycle logic into smaller components, but cautions that adding lifecycle methods to Presenters can merely relocate complex code. ### Source excerpt I have been asked several times why Presenters in Mosby (MVP library) don't have lifecycle callback methods like onCreate(Bundle), onResume() etc. Also the awesome guys over at SoundCloud have published a library called LightCycle that helps break logic out of Activity or Fragments into smaller containers bound to the parents Activity's or Fragment's lifecycle. ## Model-View-Intent on Android DevFeed: [Model-View-Intent on Android]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2016-03-04T09:00:00Z Content type: tutorial Language: en Sources: [Hannes Dorfmann]() Topics: [Android](), [ui](), [mvc](), [reactive](), [Functional programming](), [Redux](), [RxJava](), [JavaScript]() Tags: [android](), [functional-programming](), [javascript](), [model-view-intent](), [mvc](), [mvi](), [react](), [reactive](), [redux](), [rxjava](), [ui](), [view]() ### AI overview This article introduces Model-View-Intent (MVI) for Android UI architecture. It explains MVI's reliance on reactive and functional programming, relates it to MVC, and discusses influences from Redux, React, and Cycle.js. ### Source excerpt As developers we should always think outside the box. A month ago Artem Zinnatullin and I have discussed some architectural trends on android and on other platforms, like .NET and javascript, in his Podcast The Context. A few days later Christina Lee gave an awesome lightning talk Redux-ing UI Bugs during square's The Journey of Android Engineers event. ## Understanding ASP.NET 5 and .NET Core DevFeed: [Understanding ASP.NET 5 and .NET Core]() Original publisher: [Read original article]() Author: Adam Tuliper (noreply@blogger.com) Published: 2015-12-16T21:20:00Z Content type: tutorial Language: en Sources: [Adam Tuliper]() Topics: [ASP.NET](), [.NET](), [net core](), [cross-platform](), [mvc](), [C#](), [Dependency injection]() Tags: [asp-net](), [c-sharp](), [cross-platform](), [dependency-injection](), [linux](), [mvc](), [net](), [net-core](), [osx]() ### AI overview An overview of ASP.NET 5 and .NET Core, describing their modular design, cross-platform support, MVC-only architecture, unified controller model, built-in dependency injection, and self-hosting options. ### Source excerpt **Update - New ASP.NET 5 video coming soon, follow me on Twitter to keep an eye on announcements ** Most of my enterprise career was web based. In around 1997 my first major web project was to create the sign-up 3.5" floppy disks that were distributed with a good amount of Bell Atlantic phone books. This used all sorts of c-based cgi, Python scripts, and a mish mosh of tech. Things were so very very different then. We were actually the very first all Windows NT Internet Service Provider in the country. Good times but was web tech surely in its infancy. When ASP (Active Server Pages) first came out, it was amazing - it so we thought at the time as we spaghetti coded away our scripts. Fast forward nearly 20 years to ASP.NET 5. A technology that shares only letters with its predecessor. It's unbelievably fast. It runs an entirely different model than any of its predecessors. It is cross platform - even running on Linux and OSX. This is indeed a new Microsoft. What is ASP.NET 5? ASP.NET 5 is a new version of ASP.NET that has been built from the ground up with performance in mind, it is modular, and supports multiple platforms such as Windows, OSX, and Linux. ASP.NET 5 no longer contains Web Forms, it is purely MVC based and supports both C# and VB.NET. This may be a difficult point for some. Going forward, there was a lot of baggage Web Forms carried around and it was an abstraction to the web, which isn't how most modern frameworks work. As such, MVC 6 is the only supported option in ASP.NET 5. You can however still create Web Forms apps in Visual Studio 2015 (for ex. on .NET 4.6), just not for ASP.NET 5. The WebAPI technology (that released back with MVC 4) has now been merged into a unified controller model in ASP.NET 5. ASP.NET 5 now has out of the box support for Dependency Injection without the need for any third party DI containers (although several major ones work with it if that's your use case), and performance that can meet or exceed NodeJS applications. Let' ## Android Architecture: Introducing Pilot DevFeed: [Android Architecture: Introducing Pilot]() Original publisher: [Read original article]() Author: SystemDotRun Published: 2015-10-01T00:00:00Z Content type: article Language: en Sources: [SystemDotRun]() Topics: [Android](), [mvc](), [Dagger]() Tags: [android](), [android-architecture](), [architecture](), [architectures](), [controllers](), [dagger](), [fragments](), [lifecycle](), [mvc](), [mvvm](), [project](), [repo](), [view]() ### AI overview This article introduces Pilot, a work-in-progress abstract application stack for Android. It discusses managing presenter lifecycles, application flow, data scoping, and architectures based on views or a mix of fragments and views, while relating the approach to MVC, MVP, MVVM, and Dagger custom scopes. ### Source excerpt An abstract application stack for Android Motivation There are some common questions that keep popping up on the interwebs around the current collective thought on Android Architecture. Some of these questions are: What approach can I use to handle my Presenters Lifecycle? How can Presenters control the flow of an application? How can I scope data within my application? What architecture could I use to support a View only based architecture (or a mix of Fragments / Views) ? The above questions are not easy ones to address and by no means am I suggesting the below is the only solution to these common issues. I have started using a simple abstract application stack which for the kind of applications I have been developing allows a clean & structured base for them to sit on top of. This post and supporting repo is definitely a work-in-progress but Im hoping it will spark some discussion which can be fed back into the project so it's something that is useful to others also. I have been tempted to not write anything about this until I have answered all the pending questions I have myself but I feel more may be gained by publishing early and often. It is probably worth mentioning that if you are not currently using some kind of Presenter / Controller / distinct view logic abstraction in your application at present you probably will not have come across (or asked yourself) some of these questions. The same goes for Dagger (& Dagger Custom Scopes) and View only view implementations. If you have been playing with some of this stuff you may find the below more applicable. In this post I will briefly expand on the above questions and introduce the project. Preliminaries A Note on terminology Presenters are all the rage in the Android world at present. Some call them Presenters, Controllers, ViewModels, PassiveView etc and they are used as part of MVC, MVP, MVVM (with DataBinding), MVA etc and all these terms overlap and have differnt meanings and implementations depending on w ## Just learn Rails (Part 2) DevFeed: [Just learn Rails (Part 2)]() Original publisher: [Read original article]() Published: 2015-07-19T12:00:00Z Content type: opinion Language: en Sources: [Jake Yesbeck]() Topics: [Rails](), [Ruby](), [Architecture & Design](), [mvc](), [Code](), [Framework]() Tags: [code](), [framework](), [mvc](), [rails](), [ruby](), [ruby-on-rails](), [scalability]() ### AI overview This opinion article argues that Ruby on Rails can enable poor encapsulation and bad habits, especially through autoloading and ubiquitous model access. It recommends separating concerns and responsibilities to improve code comprehension and avoid scalability problems. ### Source excerpt In a previous post I explained how "just learning Rails" is not as straight forward as the phrase portrays. Even the novice programmer who learns Ruby on Rails in a methodical progression may still run into hardship. However, this is not entirely the fault of young programmer, he or she was simply enabled into bad habits. Ruby on Rails enables the complete disregard of encapsulation. Notice how I did not say that Ruby on Rails prescribes less encapsulation, it simply enables it. This idea, much like any idea posted to the Internet, is not new. Many intelligent people have come to this same realization. One such example is the Trailblazer framework, which aims to help inject some encapsulation and abstraction mechanisms Rails is lacking. (For those interested, a book has been written to more fully explain this framework). Alright, so what am I really talking about? Ruby on Rails has certain features that make it easy to forget about encapsulation. The Autoloader A keyword that most Ruby on Rails developers rarely see on a daily basis is require. A piece of Ruby on Rails magic called autoloading greatly decreased the frequency of the require keyword in Ruby on Rails applications. This has many positive aspects for new and seasoned developers alike. But, it is not without drawbacks. One such drawback is that it makes ActiveRecord objects ubiquitous. Whenever a developer has the urge to reach into the database, regardless of the context, they are able to do so. This enables horrific code. Imagine we have a view template that we want to display a user's username and their pictures. Without any guidance, this following code could come into existence: # # Reminder, this is terrible code. Never do this. #
<% User.all.each do |user| %>
<%= user.username %>
)