Flutter Developer Cheat Sheet Vocabulary

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/49

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards covering software design patterns, app architectures, Dart language features, testing types, and core Flutter concepts.

Last updated 9:02 AM on 9/27/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

50 Terms

1
New cards

Flutter

A free and open-source mobile UI framework created by Google and released in May 2017 that allows developers to create native mobile applications using a single codebase.

2
New cards

Encapsulation

The process of packaging data and related code into a single object to ensure data protection and prevent unintended access or modifications.

3
New cards

Abstraction

The process of hiding implementation details and data so programmers can focus on overall program logic.

4
New cards

Inheritance

An Object-Oriented Programming principle allowing lower classes in a hierarchy to inherit variables and methods from their parent class.

5
New cards

Polymorphism

The ability of different objects to respond differently to the same method call.

6
New cards

Hot Reload

A feature in Flutter that applies modified code changes instantly within the application.

7
New cards

Single-responsibility principle

A SOLID principle stating that every class should have only one responsibility and only one reason to change.

8
New cards

Open–closed principle

A SOLID principle stating software entities should be open for extension, but closed for modification.

9
New cards

Liskov substitution principle

A SOLID principle stating that functions using pointers or references to base classes must be able to use objects of derived classes without knowing it.

10
New cards

Interface segregation principle

A SOLID principle stating that clients should not be forced to depend upon interfaces that they do not use.

11
New cards

Dependency inversion principle

A SOLID principle stating that code should depend upon abstractions rather than concretions.

12
New cards

Dependency injection

A software design pattern where required objects are provided to instantiate a new object so that the new object does not need to construct or customize those dependencies itself.

13
New cards

Observer pattern

A design pattern defining a one-to-many dependency between objects where dependents are automatically notified and updated when state changes occur.

14
New cards

Factory

A design pattern where a factory class controls object creation and instantiation logic without specifying concrete classes directly.

15
New cards

MVC

An app architecture pattern composed of Model (data/data access layer), View (graphic display of data), and Controller (glue that alters Model based on View activity and updates View).

16
New cards

MVVM

An app architecture pattern consisting of Model, View, and ViewModel, where ViewModel serves as mediator and binds data and user action updates between View and ViewModel.

17
New cards

Presenter (MVP)

The MVP component responsible for querying the model and translating updates in the view, as the view lacks direct access to the model.

18
New cards

Clean Architecture

A concept describing how various app layers (business objects, use cases, presenters, data storage, and UI) communicate, placing MVC and MVVM at the outer presentation and UI layers.

19
New cards

Unit test

A test that verifies the correctness of a single function, method, or class under a variety of conditions, with external dependencies mocked out.

20
New cards

Widget test

A test (also called a component test) that verifies a single widget's UI appearance and interaction within a simplified lifecycle context environment.

21
New cards

Integration test

A test that verifies that all widgets and services in a complete app or large app segment work together on a real device or emulator.

22
New cards

Testing Trade-offs Comparison

A breakdown comparing Unit, Widget, and Integration tests in terms of Confidence, Maintenance cost, Dependencies, and Execution speed.

<p>A breakdown comparing Unit, Widget, and Integration tests in terms of Confidence, Maintenance cost, Dependencies, and Execution speed.</p>
23
New cards

Isolate

An independent thread in Dart that does not share memory with the main thread and communicates exclusively via messages.

24
New cards

Future

A Dart object representing a single asynchronous value or error retrieved using async/await or .then callbacks.

25
New cards

Stream

A Dart object that returns 0 or more values asynchronously over time using async* and yield.

26
New cards

Broadcast stream

A type of Stream that supports multiple attached listeners simultaneously.

27
New cards

Widget (Flutter)

An immutable description of a part of a user interface that describes configuration for an Element.

28
New cards

Element (Flutter)

An instance of a widget at a specific location in the tree that handles tree references and configuration.

29
New cards

RenderObject

An object in the render tree responsible for laying out and painting widgets displayed on screen as directed by the Element tree.

30
New cards

Mixins

A Dart construct declared with mixin or mixin class that defines reusable code across class hierarchies using the with keyword.

31
New cards

StatelessWidget

A Flutter widget that requires no mutable state and relies entirely on configuration information in itself and its BuildContext.

32
New cards

StatefulWidget

A Flutter widget with mutable state stored in a separate State object created via createState.

33
New cards

InheritedWidget

A base class widget that efficiently passes data down the widget tree to descendant children without manual constructor passing.

34
New cards

BuildContext

A locator unique to each widget that tracks its location and position within the widget tree.

35
New cards

Keys

Identifiers used in Flutter to preserve widget state and prevent unnecessary widget rebuilds.

36
New cards

List (Dart)

An ordered sequence of elements that can be fixed length or growable.

37
New cards

Set (Dart)

An unordered collection of unique values of the same type that disallows duplicate entries.

38
New cards

Map (Dart)

A key-value collection where each key is unique and associated with a value.

39
New cards

Queue (Dart)

A FIFO (First In First Out) data structure in Dart where elements added first are removed first.

40
New cards

var (Dart)

A keyword used to declare a variable whose type is inferred and fixed at compile time, preventing runtime type changes.

41
New cards

dynamic (Dart)

A type setting that disables type checking completely, allowing a variable to be reassigned to any data type at runtime.

42
New cards

Object (Dart)

The root class of the Dart type hierarchy that restricts method calls to those explicitly defined on Object.

43
New cards

final (Dart)

A variable modifier requiring single assignment via an initializer whose value cannot be reassigned once set.

44
New cards

const (Dart)

A modifier for values and objects that makes their entire deep state compile-time frozen and immutable.

45
New cards

hashCode

A single integer value representing the state of an object that affects operator == comparisons.

46
New cards

AOT Compilation (Dart)

Ahead-Of-Time compilation mode offering fast application startup and lower memory usage, but without runtime profiling optimization.

47
New cards

JIT Compilation (Dart)

Just-In-Time compilation mode using runtime profiling data for specific optimizations, but requiring longer startup and warmup periods.

48
New cards

Event Loop

The mechanism in Dart that processes asynchronous execution and queues in a non-blocking manner.

49
New cards

Event Queue

A Dart Event Loop queue containing outside events such as I/O, mouse actions, timers, drawing events, and inter-isolate messages.

50
New cards

Microtask Queue

A Dart Event Loop queue reserved for short internal asynchronous actions that execute before the Event Queue turns.