Supabase is one of the most well-known open-source alternatives to Firebase. Although Supabase implements many Firebase features, one that I constantly crave is offline support for the real-time database.

In this blog post, we’ll cover how you can use a local database as a Supabase cache through Stock, a dart package that combines multiple data sources and gets one data Stream. However, you can apply these concepts and ideas to diverse situations, such as adding offline support when using a Rest API.

To show how we can achieve that, we’ll create a simple app that lists all of Xmartlabs’ open-source projects, demonstrating how Stock helps us achieve excellent results.

Architecture Overview

Although we want to build a simple app, we’ll use the repository pattern, one of the most used patterns in Flutter nowadays. If you don’t know about it, I suggest checking out this blog.

We’ll have two data sources, a remote and a local data source, which Stock will combine in the repository.

Because we want to use the real-time database, we’ll use the [Supabase Flutter package]. Although the package provides many features, you can use Supabase as a REST API.

Your local database will store this data. In our case, we’ll use Floor because it’s simple and has many features. If you’d prefer to use another one, there are a bunch of alternatives, such as Drift or Realm, you can use.

We will use a StatefulWidget to display the data to simplify this Project. However, in an actual project, you should use a state management package, like Bloc or Provider.

Sample app: listing our company’s OSS projects

As mentioned, we want to build an app that displays Xmartlabs’ Open Source projects.

Here’s how it will look:

First, we have to create a new Flutter project and the project’s entity.

class Project extends Equatable {
  final int id;
  final String name;
  final String description;
  final String url;
  final String imageUrl;
  final String language;

  // Ommited: Add constuctor, define props for equals and hashcode and add `fromJson` method

See the full implementation here.

Step 1: Remote Source - Supabase setup

Supabase setup is not complex, and there are good tutorials showing how you can do this process. In this case, I created a Supabase free project which contains only one table, projects. This table is where the metadata for Xmartlabs’ open-source projects will be stored.

Then I included the supabase_flutter package in the Flutter project. I initialized the Supabase client and created the ProjectSupabaseRemoteSource with only one method that gets a Stream of projects using the Real Time Database.

  final client = await Supabase.initialize(
    url: Config.supabaseUrl,
    anonKey: Config.supabaseAnonKey,
  ).then((supabase) => supabase.client);
class ProjectSupabaseRemoteSource {
  final SupabaseClient _client;


  Stream<List<Project>> getRemoteProjectsStream() => _client
      .map((json) =>;

You can see the full Supabase integration in this commit.

Step 2: Local Source - Local Database setup

In this example, we’ll use Floor, a simple and powerful Data Base in Flutter.

Usually, we use separate entities for database and service, depending on your Project’s complexity. In this case, we’ll use the same Project entity instead of different ones.

After the setup, you will have two main classes:

  • The Project entity will be mapped to a table.
  • The DAO, which, in this case, will be our local source. This class will have methods for getting and updating the database projects.
@Entity(tableName: 'projects')
class Project extends Equatable {
  final int id;
  // ... other fields
abstract class ProjectLocalSource {
  @Query('SELECT * FROM projects')
  Stream<List<Project>> getProjects();

  @Insert(onConflict: OnConflictStrategy.replace)
  Future<void> insertProjects(List<Project> projects);

  @Query('DELETE FROM projects')
  Future<void> deleteAllProjects();

  Future<void> replaceProjects(List<Project> projects) async {
    await deleteAllProjects();
    await insertProjects(projects);

You can check the full database integration here.

Step 3: Repository - Stock Integration

The previous steps were not difficult. We created one entity and a couple of data sources. However, this is the most exciting part, where we have to combine different data sources to get only one stream that contains the OSS projects.

We will use Stock, a dart package whose primary function is to combine these sources. We need to provide Stock with two essential classes:

  • Fetcher: a class to fetch the network data. Stock provides two types of fetchers.
    • Stream, ideal for this case, in which we use the Real Time Database.
    • Future, used, for example, if you are consuming a REST API.
  • SourceOfTruth: a class that can store the fetched data in a local cache. In our case, the local cache is our Floor database.

Two types define these classes:

  • The Key, a type commonly used to get de data. That key can have important information like an id or the current page number if you are fetching a list. In our example, we won’t use it because we will bring all data just using one endpoint.
  • The entity class, in our example a List<Project>. The Fetcher and the SourceOfTruth could use different types, but they should be mapped to the same type using a StockTypeMapper.
class ProjectRepository {
  final Stock<dynamic, List<Project>> _stock;

    ProjectLocalSource projectLocalSource,
    ProjectSupabaseRemoteSource projectRemoteSource,
  ) : _stock = Stock<dynamic, List<Project>>(
          fetcher: Fetcher.ofStream(
            (_) => projectRemoteSource.getRemoteProjectsStream(),
          sourceOfTruth: SourceOfTruth<dynamic, List<Project>>(
            reader: (_) => projectLocalSource.getProjects(),
            writer: (_, projects) =>
                projectLocalSource.replaceProjects(projects ?? []),

  Stream<StockResponse<List<Project>>> getProjects() =>;

Stock provides a Stream of StockResponse, which has three possible values: StockResponseLoading, StockResponseData, or StockResponseError. With that Stream, we are ready to display the data and status in the UI.

Inspect the full implementation in this commit.

Step 4: Handle stock responses

In this last part, we’ll handle the three different response types: the error, the data, and the loading state. To do that we will handle the responses in a StatefulWidget

The widget state will contain the list of projects and a bool that indicates if the data is loading or not.

class _OssProjectsPageState extends State<OssProjectsPage> {
  late StreamSubscription _subscription;

  List<Project>? projects;
  bool isLoading = false;

  void initState() {
    _subscription = projectRepository.getProjects().listen((response) {
      if (response.isData) {
        setState(() {
          projects = response.requireData();
          if (isLoading && response.origin == ResponseOrigin.fetcher) {
            isLoading = false;
      } else if (response.isLoading) {
        setState(() => isLoading = true);
      } else {
        if (isLoading && response.origin == ResponseOrigin.fetcher) {
          setState(() => isLoading = false);
          content: Text(
            'An error happened!: ${(response as StockResponseError).error}',

  void dispose() {

So the last thing is using the state to display the data:

class _OssProjectsPageState extends State<OssProjectsPage> {
  //.... previous code
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Xmartlabs OSS Projects')),
      body: Stack(
        children: [
            padding: const EdgeInsets.all(8.0),
            itemCount: projects?.length ?? 0,
            itemBuilder: (context, index) =>
                _ProjectWidget(project: projects![index]),
          if (isLoading) const CircularProgressIndicator(),

And this is the end result!

As you can see, the OSS projects are displayed fast, and there’s no difference between online and offline.

The complete example is on GitHub, so go ahead and check it out!


This blog analyzed how we can integrate offline support easily to Supabase. Furthermore, if we replace Supabase with another provider or simply use a rest API, the code will be the same. So if your data layer changes, you don’t have to make any changes to your presentation layer, which is one of the essential aspects of this architecture.

In my experience, offline support moves app experience to the next level. You can remove ugly spinners and give feedback to the user instantly. So making an effort to achieve it is worth it.

We also had a glimpse of how Stock helped us to get this feature. The package did the most challenging tasks, such as synchronizations, state reporting, and data storing, allowing the app to run extremely fast.

I encourage you to try it out and share your feedback and contributions!