An overview of the Factory Method design pattern and its implementation in Dart and Flutter
Previously in the series, I analysed a design pattern that is commonly used in our day-to-day programming, sometimes even without considering it - Iterator. In this article, I would like to analyse and implement one of the creational design patterns - Factory Method.
An overview of the Iterator design pattern and its implementation in Dart and Flutter
In the last article, I analyzed one of the behavioural design patterns - Interpreter. This time I would like to represent the pattern which specific implementation(s) you have probably already used in your day-to-day programming without even noticing or considering it - the Iterator design pattern.
An overview of the Interpreter design pattern and its implementation in Dart and Flutter
Previously in the series, I analysed a relatively simple and straightforward design pattern — Facade. In this article, I will analyse and implement a pattern, which has a similar structure to Composite but is used in a different context and for a different purpose — the Interpreter design pattern.
An overview of the Facade design pattern and its implementation in Dart and Flutter
In the last article, I analysed one of the behavioural design patterns - State. This time, I would like to represent a pattern that you have probably already used as a developer, but just did not realise that it is a design pattern at all. Therefore, let me introduce you to Facade.
An overview of the State design pattern and its implementation in Dart and Flutter
Previously in the series, I have analysed one of the most practical design patterns you can use in day-to-day coding - Strategy. In this article, I will analyse and implement a pattern, which has a similar structure to Strategy but is used for a different purpose - the State design pattern.
An overview of the Strategy design pattern and its implementation in Dart and Flutter
In the last article, I have represented the Composite design pattern. This time, I would like to analyse and implement a design pattern that belongs to the category of behavioural design patterns — Strategy.
An overview of the Composite design pattern and its implementation in Dart and Flutter
In the last article, I analysed the Template Method design pattern. This time I would like to represent the pattern which is pretty simple to understand (compared to the other design patterns) and is related to the implementation of the Flutter framework itself - the Composite design pattern.
An overview of the Template Method design pattern and its implementation in Dart and Flutter
Previously in the series, I analysed one of the most common and useful design patterns available - Adapter. In this article, I would like to analyse and implement one of the behavioural design patterns - Template Method.
An overview of the Adapter design pattern and its implementation in Dart and Flutter
In the last article, I analysed the first design pattern in the series — Singleton, provided some general thoughts about its structure, applicability, pros and cons, implemented it in several different ways. This time, I would like to analyse and implement a design pattern that belongs to the category of structural design patterns — Adapter.
An overview of the Singleton design pattern and its implementation in Dart and Flutter
First of all, I would like to thank you all for the support after publishing the introduction article to this series. Honestly, I have not expected that amount of people to not only be interested in the creation of mobile applications using Flutter but who are also willing to learn more about the Dart language itself, OOP design patterns and their appliance, code architecture or software engineering in general. This encouraged me to dive straight into the research, coding, and hence, I present to you the first design pattern in the series — Singleton.