Coordinator-MVVM-Rx-Example - Example of MVVM-C architecture implemented with RxSwift

  •        35

This simple app displays a list of the most starred repositories on GitHub by a language. User can choose a language to filter repositories and select repository in the list to open it in the SFSafariViewController. App is written with Xcode 8 and Swift 3.

https://github.com/uptechteam/Coordinator-MVVM-Rx-Example

Tags
Implementation
License
Platform

   




Related Projects

RxCoordinator - 🎌 Reactive navigation library for iOS based on the coordinator pattern

  •    Swift

“How does an app transition from a ViewController to another?”. This question is common and puzzling regarding iOS development. There are many answers, as every architecture has different implementation variations. Some do it from the view controller, while some do it using a router/coordinator, which is an object that connects view models. Setup the root view controller in the AppDelegate.

XCoordinator - 🎌 Powerful navigation library for iOS based on the coordinator pattern

  •    Swift

⚠️ We have recently released XCoordinator 2.0. Make sure to read this section before migrating. In general, please replace all AnyRouter by either UnownedRouter (in viewControllers, viewModels or references to parent coordinators) or StrongRouter in your AppDelegate or for references to child coordinators. In addition to that, the rootViewController is now injected into the initializer instead of being created in the Coordinator.generateRootViewController method. “How does an app transition from one view controller to another?”. This question is common and puzzling regarding iOS development. There are many answers, as every architecture has different implementation variations. Some do it from within the implementation of a view controller, while some use a router/coordinator, an object connecting view models.

ios-architecture - A collection of iOS architectures - MVC, MVVM, MVVM+RxSwift, VIPER, RIBs and many others

  •    Swift

This repository hosts each sample app in separate directory. ⭐️ Click the title of example to see detailed README information about specific architecture.

CleanArchitectureRxSwift - Example of Clean Architecture of iOS app using RxSwift

  •    Swift

The Platform is a concrete implementation of the Domain in a specific platform like iOS. It does hide all implementation details. For example Database implementation whether it is CoreData, Realm, SQLite etc. Application is responsible for delivering information to the user and handling user input. It can be implemented with any delivery pattern e.g (MVVM, MVC, MVP). This is the place for your UIViews and UIViewControllers. As you will see from the example app, ViewControllers are completely independent of the Platform. The only responsibility of a view controller is to "bind" the UI to the Domain to make things happen. In fact, in the current example we are using the same view controller for Realm and CoreData.

RxFlow - RxFlow is a navigation framework for iOS applications based on a Reactive Flow Coordinator pattern

  •    Swift

RxFlow is a navigation framework for iOS applications based on a Flow Coordinator pattern. This README is a short story of the whole conception process that led me to this framework.


SwinjectMVVMExample - An example to use Swinject in MVVM architecture with ReactiveCococa

  •    Swift

This is an example project to demonstrate dependency injection and Swinject in MVVM (Model-View-ViewModel) architecture with ReactiveCocoa. The app asynchronously searches, downloads and displays images obtained from Pixabay via its API. The following blog posts demonstrate step-by-step development of the project.

RxViewModel - ReactiveViewModel-esque using RxSwift

  •    Swift

The Model-View-ViewModel (MVVM) pattern is an application pattern that isolates the user interface from the underlying business logic. MVVM belongs to a class of patterns called Separated Presentation. These patterns provide a clean separation between the UI and the rest of the application. This improves the testability of the application and allows the application and its UI to evolve more easily and independently. The Model-View-ViewModel (MVVM) pattern helps you to cleanly separate the business and presentation logic of your application from its user interface (UI). Maintaining a clean separation between application logic and UI helps to address numerous development and design issues and can make your application much easier to test, maintain, and evolve. It can also greatly improve code re-use opportunities and allows developers and UI designers to more easily collaborate when developing their respective parts of the application.

MVVM-IOS-Example - A basic example of a way to implement MVVM using ReactiveCocoa

  •    Objective-C

#MVVM iOS Example This is the accompanying source code to an article I wrote to demonstrate a basic MVVM implementation. ReactiveCocoa and its dependencies are all self contained within this project. ##License This source code is made available under the MIT License.

People-MVVM - Android Sample to explain Model View View Model and DataBinding in android applications

  •    Java

Example android Model View View Model and DataBinding used to explain how to use this pattern in our android applications. This example was created to support an article explanation Escribiendo android apps con Data Binding (spanish) and also it was created for a talk MVVM-android Meetup Androidinights by GDG Androidtitlan Mexico City March 2016.

countries - An example Android app using Retrofit, Realm, Parceler, Dagger and the MVVM pattern with the data binding lib

  •    Kotlin

A sample Android app written in Kotlin, which lists all countries with some additional information (currencies, languages, …). The app uses the MVVM pattern with the Android data binding lib. Countries can be bookmarked and are then stored locally with Realm. Retrofit is used to fetch the country information from the free REST Countries service. For JSON parsing, custom Gson TypeAdapters are used. PaperParcel is used to make the Country objects Parcelable. Also, Dagger 2 is used for dependency injection. This project can also be used as a template for new apps. Check out the template branch for a cleaned up version of this project.

ReactiveProperty - MVVM Extensions for Rx

  •    

ReactiveProperty is MVVM and Asynchronous Extensions for Reactive Extensions. Target Framework is .NET 4.0 Client Profile, Silverlight 4, Windows Phone 7.1.

Theatre - Pet project using Clean Architecture + MVVM + Reactive Extensions + Android Architecture Components

  •    Kotlin

Pet project using Clean Architecture + MVVM + Reactive Extensions + Android Architecture Components. The data is fetched from LondonTheatreDirect API. The overriding rule of this architecture says that the source code dependencies always point inwards. The outer tiers can only dependent of inner tiers. Therefore, the inner tiers know nothing about the outer tiers. The more further you go through the concentric circles, the higher level the software becomes. Which means that the level of abstraction increases.

ReactiveProperty - ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions

  •    CSharp

ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions. Target framework is .NET 4.6, UWP, Xamarin.iOS, Xamarin.Android, Xamarin.Mac, Xamarin.Forms and .NET Standard 1.3. ReactiveProperty is very powful and simple library.

welcome-coordinator - Welcome Coordinator for Android

  •    Java

Welcome Coordinator is a library for Android that will help you create really awesome welcome wizards for your apps, but that's not all. You can also use the library to create form wizards really nicely. Take a look to how you would integrate Welcome Coordinator into your app. Add the library dependency to your build.gradle file.

WPF Application Framework (WAF)

  •    WPF

The WPF Application Framework (WAF) is a lightweight Framework that helps you to create well structured WPF Applications. It supports you in applying a Layered Architecture and the Model-View-ViewModel (aka MVVM, M-V-VM, PresentationModel) pattern.