Feat/build native android apps with android solid services by erfangholami · Pull Request #23 · solid/dev

erfangholami · 2026-04-25T11:53:52Z

Add a guide for native Android developers to integrate Solid into their apps with the help of AndroidSolidServices project.
It presents developers with two different methods for integration based on their use-case.

…lidServices

jeswr · 2026-04-25T14:55:55Z

Thank you for this contribution @erfangholami!

Before we merge, I ask that this library could be given a different short-name - even if just used in this documentation. I suggest SolidAndroidService (SAS).

The documentation on Authentication, and Read/Write are great contributions well-suited to this repository.

The documentation based around use of Data Modules warrants further discussion. There are divergent approaches to interoperability in the Solid ecosystem at present; as such, I would consider documentation related to Data Modules in general to be opinionated. The ODI, for instance, has propose the shapes repository as a way of tracking and aligning on data models used in the ecosystem. The fact that the Chat Spec is used as an example, does somewhat resolve this. My suggestion is that we keep this in the docs, and add clear warnings - here, and in SAS itself - about what is based on:

Specifications (and, if so, identify the version no. & maturity of the specification referenced), here I expect you to need to reference:
- https://solidproject.org/TR/2024/protocol-20240512
- https://solidproject.org/TR/oidc (most likely publish snapshot of pre 0.1 version (spec+primer) solid-oidc#250 once merged)
- https://solid.github.io/chat/
Best practise / implementors knowledge; and where that knowledge comes from (I expect this to be anything else in the data modules)

erfangholami · 2026-04-26T23:52:57Z

I have added two matters you have mentioned. Let me know if they are well-described or need more modifications.

jeswr · 2026-04-30T11:22:38Z

Thanks @erfangholami - @matthieubosquet @langsamu as you have more Java experience could one of you please provide an additional review.

langsamu

Thank you. Great contribution.

In addition to the comments inline, may I recommend a starter project (or two) that would give users an easy way to start. See how some of the other guides in this repo do this.

langsamu · 2026-05-11T14:16:54Z

+
+## 1. Install the SAS Host App
+
+If you are using **SAC**, the SAS host app must be installed on the device. Download the latest APK from the [GitHub Releases](https://github.com/pondersource/Android-Solid-Services/releases) page, enable *Install from unknown sources* in device settings, and install it. Launch the app and sign in with your Solid pod credentials.


Could you please write about why one must enable installing from unknown sources.

Are there plans to go on the official marketplace? When? Why not?
What should developers consider when they enable this.
Where should they enable this and where, if any, should they not.

langsamu · 2026-05-11T14:29:51Z

+                        authorizationException
+                    )
+
+                } catch (_: Exception) {}    


Please don't guide readers towards swallowing exceptions.

If there is a good reason for this then please document with inline comment and outside the sample code.

If there isn't then please modify and instead guide users in how they should avoid and handle exceptional cases.

langsamu · 2026-05-11T14:31:42Z

+                logoutRedirectUrl = YOUR_LOGOUT_REDIRECT_URL
+            )
+            return intent
+            //intent would be null if failed to make the intent and can read errorMessage.


Please improve this phrasing.

langsamu · 2026-05-11T14:34:02Z

+
+=== "SolidAndroidApi"
+
+    The `Authenticator` class manages an OpenID Connect session with DPoP support. It opens a browser tab for the user to log in, then processes the authorization callback your app receives.


What about Solid servers that don't support DPoP?

What about PKCE?

langsamu · 2026-05-11T14:35:02Z

+                redirectUri = AUTH_APP_REDIRECT_URL //YOUR_APP_PACKAGE_NAME:/oauth2redirect
+            )
+            return intent
+            //Handle the intent in your ComposeComponent/Activity/Fragment.


Could you please use consisten whitespace style in comments.

Suggested change

//Handle the intent in your ComposeComponent/Activity/Fragment.

// Handle the intent in your ComposeComponent/Activity/Fragment.

langsamu · 2026-05-11T14:37:33Z

+                    if (connected) {
+                        val account = signInClient.getAccount()
+                        if (account == null) {
+                            // No access grant yet — ask the user to approve


Access grant is quite a loaded term in the context of Solid. Are you sure that you want those connotations?

I think you mean something else here. Could you please use different terminology.

I might have misunderstood something, of course.

langsamu · 2026-05-11T14:40:53Z

+                    // Fetch the authenticated user's WebID document
+                    val webId = resourceClient.getWebId()


This feature of the library is worth explaining to users.

But it does not seem relevant to the rest of CRUD operations showcased here.

It might also be confusing, since WebID profile documents are not required to be Solid resources and are best requested without authentication, because they are almost always public.

May I suggest separating.

langsamu · 2026-05-11T14:42:29Z

+                    )
+
+                    // Create a new resource on the pod
+                    val newNote = MyNote(body = "Hello Solid!")


MyNote caught me by surprise.
Perhaps comment something like see below.

langsamu · 2026-05-11T14:44:36Z

+    }
+    ```
+
+    Your data classes must extend `RDFSource` or `NonRDFSource` from the shared module:


It might be worth to expand this following section.

How does one do something meaningful with the data in an RDFSource?

How does one work with NonRDFSource?

erfangholami added 2 commits April 25, 2026 13:50

add tabbed extension to mkdocs

ffae46f

feat: add guide for building native Android Solid apps with AndroidSo…

784e733

…lidServices

erfangholami requested a review from a team as a code owner April 25, 2026 11:53

erfangholami added 2 commits April 27, 2026 01:48

Add specifications or best practice implementation for each section

eb99917

Change project name in this guide and use abbreviations

ec8531b

langsamu requested changes May 11, 2026

View reviewed changes


		## 1. Install the SAS Host App

		If you are using SAC, the SAS host app must be installed on the device. Download the latest APK from the [GitHub Releases](https://github.com/pondersource/Android-Solid-Services/releases) page, enable Install from unknown sources in device settings, and install it. Launch the app and sign in with your Solid pod credentials.


		=== "SolidAndroidApi"

		The `Authenticator` class manages an OpenID Connect session with DPoP support. It opens a browser tab for the user to log in, then processes the authorization callback your app receives.

	//Handle the intent in your ComposeComponent/Activity/Fragment.
	// Handle the intent in your ComposeComponent/Activity/Fragment.

		// Fetch the authenticated user's WebID document
		val webId = resourceClient.getWebId()

Conversation

erfangholami commented Apr 25, 2026

Uh oh!

jeswr commented Apr 25, 2026

Uh oh!

erfangholami commented Apr 26, 2026

Uh oh!

jeswr commented Apr 30, 2026

Uh oh!

langsamu left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants