fOSlink - farmOS mobile app

pat · April 7, 2026, 1:32pm

Inspired by a project of @Farmer-Ed I started to craft a mobile app to help adding data to farmOS.

It is made with help of Claud CODE and is built with Svelte.
For now it’s running on my server, but I intend to release it as a plain mobile app on FDroid.org.
If all goes well, it should work on all instances of farmOS via the API.

Not too fancy and flexible, but workable for basic logging. I made it for my own use, but it may be useful for others as well.

Feel free to try. I will translate it to English, and update here on bigger changes.
Edit: I should add that it’s only tested on farmOS v 3.x

Supports activity, observation, maintenance logs with assets and image upload.
I also tried to mimic the planting quickform.

mstenta · April 7, 2026, 2:18pm

Cool! Looks great @pat!

The only major change you might need to be aware of in v4 is that assets no longer have a status field. They have a boolean archived field only. So if you are using status then you might want to plan ahead for that.

pat · April 9, 2026, 4:07pm

So… long dream come true. I got myself an android app.

It’s kind of like the FieldKit app, but propably not as flexible.
It works fine for me to add different logs in an easy way.

It’s released in F-Droid. To try it you would need to add the repo in F-Droid since I have not made it to the official repo yet. Instructions in url below:

Updated the app-info with screenshots and more info, but it seems to take some time to sync.

Currently the app connects to a specific consumer (See the repo for info : BitfieldFarm/foslink-app - Codeberg.org ) This lets the user add the farmOS url, and the user is taken to the farmOS login page to autorize the app.

@mstenta I think my own "farm” consumer is tweaked a bit from the standard.
One of my goals was to have this app work on plain Farmier instances as well.
Any advise on that matter?

pat · April 9, 2026, 4:10pm

Todo:

The todo-view hides overdue tasks by default. Just tap overdue to show them.

Today, This week and This month buttons have two functions.
A second tap changes to next period.

Today - Tomorrow

This week - Next week

This Month - Next Month

mstenta · April 9, 2026, 4:47pm

The “proper” way to do this would be for there to be a consumer in farmOS that is specifically for your app. This could be packaged into a super simple companion module, which only creates the consumer (and deletes it if the module is uninstalled).

Here are two examples, from the Field Kit module and the SurveyStack module:

github.com/farmOS/farm_fieldkit

farm_fieldkit.install

4.x

<?php

/**
 * @file
 * Install, update and uninstall function for the farm_fieldkit module.
 */

declare(strict_types=1);

use Drupal\consumers\Entity\Consumer;
use Drupal\simple_oauth\Oauth2ScopeInterface;

/**
 * Implements hook_install().
 */
function farm_fieldkit_install() {

  // Check for default role scopes.
  /** @var \Drupal\simple_oauth\Oauth2ScopeProviderInterface $scope_provider */
  $scope_provider = \Drupal::service('simple_oauth.oauth2_scope.provider');

This file has been truncated. show original

github.com/mstenta/farm_surveystack

farm_surveystack.install

3.x

<?php

/**
 * farmOS SurveyStack install functions.
 */

use Drupal\consumers\Entity\Consumer;

/**
 * Implements hook_install().
 */
function farm_surveystack_install() {

  // Create an "SurveyStack.io Aggregator" consumer.
  $consumer = Consumer::create([
    'label' => 'SurveyStack.io Aggregator',
    'client_id' => 'surveystack_aggregator',
    'grant_types' => [
      'authorization_code',
      'refresh_token',

This file has been truncated. show original

Those are just the *.install files of the module… and you can see they have a *_install() function and a *_uninstall() function, which creates/deletes the consumer, respectively.

The only other file you need is a *.info.yml file to declare the module’s info. That’s it.

Regarding Farmier - if you want to create a module like that, I can make it available to Farmier users.

pat · April 9, 2026, 5:35pm

That makes sense. It’s how I did it for me in the first place.
I should try to make that module then.