# MVC Published articles for MVC. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Use C# unions and closed hierarchies in ASP.NET Core DevFeed: [Use C# unions and closed hierarchies in ASP.NET Core]() Original publisher: [Read original article]() Author: Dmitrii Korolev Published: 2026-09-10T17:00:00Z Content type: tutorial Language: en Sources: [.NET Blog]() Topics: [C# 15](), [ASP.NET Core](), [.NET](), [Polymorphism]() Tags: [asp-net-core](), [blazor](), [c-sharp](), [c-sharp-15](), [closed-hierarchies](), [json](), [minimal-api](), [mvc](), [net](), [net-11](), [openapi](), [polymorphism](), [signalr](), [system-text-json](), [union-types]() ### AI overview Explains how C# unions and closed hierarchies model API values with a fixed set of possible types in ASP.NET Core. It contrasts unions with open inheritance-based polymorphism and describes System.Text.Json support. ### Source excerpt Learn how C# unions and closed hierarchies work with System.Text.Json across ASP.NET Core Minimal APIs, MVC, SignalR, Blazor, and OpenAPI. The post Use C# unions and closed hierarchies in ASP.NET Core appeared first on .NET Blog. ## 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. ## Essential Annotations Every Spring Developer Should Know DevFeed: [Essential Annotations Every Spring Developer Should Know]() Original publisher: [Read original article]() Author: Nelson Djalo Published: 2024-10-08T16:03:11Z Content type: tutorial Language: en Sources: [Amigoscode Newsletter]() Topics: [Spring Boot](), [Java](), [Application Development](), [configuration](), [Spring MVC](), [HTTP](), [JSON](), [XML]() Tags: [application-development](), [developer](), [http](), [java](), [json](), [mvc](), [spring](), [spring-boot](), [xml]() ### AI overview A tutorial explaining commonly used Spring Boot annotations for configuring applications, managing dependencies, enabling auto-configuration, scanning components, defining MVC controllers, handling HTTP responses, and binding URL and request parameters. ### Source excerpt Understanding Key Annotations for Simplified Development ## Understanding Non-Blocking Services with Kotlin Coroutines and Spring Boot DevFeed: [Understanding Non-Blocking Services with Kotlin Coroutines and Spring Boot]() Original publisher: [Read original article]() Published: 2024-03-25T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Spring Boot](), [Kotlin](), [Spring MVC](), [Programming]() Tags: [coroutines](), [kotlin](), [mvc](), [programming](), [spring](), [spring-boot](), [workshop-learning-programming]() ### AI overview This tutorial examines blocking request handling in Spring Boot and Spring MVC, then introduces Kotlin Coroutines as a way to model non-blocking services. It uses a simple greeting service to illustrate thread usage and request processing. ### Source excerpt From blocking to non-blocking with Kotlin, Coroutines and Spring Boot ## VIPER Architecture for iOS Apps DevFeed: [VIPER Architecture for iOS Apps]() Original publisher: [Read original article]() Author: Surbhi Gupta Published: 2023-05-18T14:59:24Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [iOS](), [Code](), [business logic](), [ui](), [navigation](), [mvc]() Tags: [apps](), [architecture](), [business-logic](), [code](), [controllers](), [flow](), [ios](), [modular](), [mvc](), [mvvm](), [navigation](), [patterns](), [swift](), [ui](), [viper]() ### AI overview This tutorial explains VIPER, an architectural pattern for iOS apps. It describes how VIPER divides each module into View, Presenter, Interactor, Entity, and Router components, with separate responsibilities and delegation-based communication. ### Source excerpt What is a Good Architecture? Architecture serves as a blueprint for a system. It provides a mechanism to communicate between various components and abstracts the complexity. It is important to separate out code components so that they are identifiable, serve a single purpose/responsibility and also fit logically. Code should be scalable, stable upon expansion, and flexible, which brings in the need for a good architecture. A good architecture not only helps in the success of the product but also allows for easy maintenance and makes people's lives easier. This article will talk about VIPER architecture, which is used to build many large projects. What is VIPER? VIPER is an architectural pattern like MVC and MVVM. One of the major issues with MVC and MVVM is bulky controllers. VIPER solves this problem by following Single Responsibility Principle and making the code more modular. Flow of Control Each module created with VIPER has five classes, each with their own responsibilities. No class does anything other than the specified role. These classes are listed below: View: It is responsible for only maintaining and displaying the view. It picks up any user interactions and passes the information to the presenter to decide the next step. Unlike other architecture patterns like MVC or MVVM, its sole responsibility is to manage and show the UI. Presenter: It is the only class that interacts with all other components except Entity. It is the decision-making engine for routing the flow. Interactor: It interacts with Entity and contains business logic. This class is where all the API calls and database interactions are added. Entity: Data model that is used by the interactor. Router: It does all the wire-framing or navigation from one module to another based on the information passed by the presenter. An ideal folder structure would be like below: Ideal Folder Structure with VIPER The communication between various components follows a delegation pattern. One component calls ## 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. ## Что случилось с GUI-фреймворками? DevFeed: [Что случилось с GUI-фреймворками?]() Original publisher: [Read original article]() Published: 2019-04-12T21:46:29Z Content type: opinion Language: ru Sources: [Tonsky Стой под стрелой]() Topics: [GUI](), [ui](), [SVG]() Tags: [flat](), [gui](), [livejournal](), [mvc](), [svg](), [tag-5e1c061eda96](), [tag-c40b78a8c8a6](), [tag-d16a2c26554f](), [tag-e3028c5e0ab2](), [ui]() ### AI overview The author discusses what a desktop GUI framework should provide, arguing that customizable low-level primitives and core capabilities such as input handling, scrolling, rendering, font output, and DPI handling are more valuable than large collections of ready-made widgets or platform-specific look and feel. The article expresses a preference for designing polished interfaces directly and cautions against imposing patterns such as MVC or VDOM. ### Source excerpt Это третий пост в моем квесте по поиску GUI-фреймворка для десктопных приложений. Первый, второй. Давайте немного сориентирую, что я ищу. Для многих "GUI-фреймворк" почти равно библиотека виджетов, чем больше тем лучше. Чтобы GUI собрать из кубиков лего минимальными силами. Меня это не очень возбуждает, потому что универсальных виджетов мало, а что-то более интересное надо делать под себя все равно. Поэтому для фреймворка важнее "уметь доделать свое", чем "побольше готового". Также популярно мнение что GUI-фреймворк это look and feel, платформенно-зависимый или же просто не вырвиглазный. Типа это сложная часть, повторить лук платформы. Мне тоже пофиг. Дело в том, что сейчас самое идеальное время для GUI-фреймворка: все наигрались в игру "сделай look and feel как настоящий" и привыкли к веб-приложениям, где вообще каждый первый сайт разный. Плюс в моду вошел flat и минимализм, то есть виджеты рисовать дешево и просто, как никогда. А платформенный look and feel это иллюзия, все равно в каждом реальном приложении миллион случаев, которые не укладываются в стандартные checkbox/input/dropdown. И чем больше приложение, тем больше надо тюнить и дорисовывать самому. UI это не лего, его надо дизайнить и рисовать как целое, тогда будет гармонично. Таким образом, от GUI фреймворка мне бы хотелось иметь базовые сложные вещи покрытыми (платформенно-зависимая обработка ввода, скроллинг, быстрый рендеринг, вывод шрифтов, dpi handling), какие-то базовые графические примитивы (прямоугольник там, линия, градиент, тенюшечки, svg) и возможность залезть под капот и все застайлить и запрогать как хочется. Я НЕ ищу сокращения затрат на дизайнера за счет использования готовых компонент/дефолтного look and feel. Меня интересует возможность потратить много и долго, но сделать самому и хорошо, чем кое-как и из готового. Pixel-перфект и именно так, как мне нужно, а не так, как автор фреймворка сделал и сейчас уже хрен отковыряешь. Качественное вылизанное end-user приложение, а не дешево выгляд ## 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" ## How We Develop New Features Using Offsites and Clean Architecture DevFeed: [How We Develop New Features Using Offsites and Clean Architecture]() Original publisher: [Read original article]() Published: 2018-11-02T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Architecture & Design](), [iOS](), [Swift](), [Objective-C](), [mvc](), [App]() Tags: [app](), [apple](), [architecture](), [bug](), [code](), [engineering](), [ios](), [mvc](), [new-feature](), [swift]() ### AI overview SoundCloud describes how its iOS team developed new features while modernizing a large legacy codebase containing Objective-C and Swift. The team adopted the VIPER architectural pattern, compared with MVC, and used it successfully for the Mini Player and later features. The article also explains how project kickoffs and focused offsites support feature planning, brainstorming, and team productivity. ### Source excerpt The current SoundCloud iOS App was built back in 2014, resulting in a huge codebase consisting of both Objective-C and Swift, with multiple... ## Building Shopify POS for Android Using MVVM DevFeed: [Building Shopify POS for Android Using MVVM]() Original publisher: [Read original article]() Author: Richa Khanna Published: 2018-10-31T17:30:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Android](), [mvc]() Tags: [android](), [architecture](), [architectures](), [developers](), [mvc](), [onboarding](), [shopify](), [state](), [testing](), [user-interface]() ### AI overview This article explains why Shopify standardized its Android POS app on the Model-View-ViewModel (MVVM) architecture. It describes the earlier use of MVC and MVP, the benefits of consistency, state retention, separation of concerns, testing, and onboarding, and the gradual migration strategy for legacy screens. ### Source excerpt There are many architectures out there to structure your app. The one we use in Shopify's Point of Sale (POS) for Android app is the Model-View-ViewModel (MVVM) pattern based on Google's App Architecture Guide which was announced last year at Google I/O 2017. Shopify POS History Our POS app is three and a half years old, and we didn't build it using MVVM from scratch. ## 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. ## Events in spring v2 DevFeed: [Events in spring v2]() Original publisher: [Read original article]() Published: 2017-09-29T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [async](), [Exception](), [mvc]() Tags: [asynchronous](), [errors](), [event](), [exceptions](), [handler](), [mvc](), [spring]() ### AI overview This tutorial explains advanced event handling in Spring applications, including ordered handlers, asynchronous processing, and exception handling. It describes using @Order, @Async, custom executors, and custom error handlers, and notes that exceptions can stop further event propagation by default. ### Source excerpt Last time I wrote about events in a spring based application I've introduced some basics on how events can be dispatched using spring infrastructure. In this post, I'm going to dig deeper into an order of handlers, exceptions and asynchronous events handlers. Read more ## 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. ## Lessons from Square's College Code Camp DevFeed: [Lessons from Square's College Code Camp]() Original publisher: [Read original article]() Author: Elana Tee Published: 2016-09-13T18:10:41Z Content type: opinion Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Development](), [Rails](), [Ruby](), [Web Development](), [iOS](), [Mobile](), [mvc]() Tags: [developers](), [development](), [engineering](), [ios](), [mobile](), [mvc](), [rails](), [ruby](), [web-development]() ### AI overview A personal reflection on Square's five-day College Code Camp, covering technical workshops in Ruby, Rails, design, iOS, and web development, as well as mentorship and leadership experiences. ### Source excerpt Lessons learned at Square's College Code Camp [Next page]()