Google Summer of Code 2026

[nicolas-raoul]

Everyone interested in GSoC 2026, welcome!

Please read the instructions to apply.

Thank you :-)

[shankarpriyank]

hi @nicolas-raoul
which one of the projects has more priority ?
the edit feature or App modularization + Jetpack Compose?

[nicolas-raoul]

@shankarpriyank Same priority. Our intention is to have both projects as GSoCs this year (with at least 2 mentors on each). 😊

[shankarpriyank]

@shankarpriyank Same priority. Our intention is to have both projects as GSoCs this year (with at least 2 mentors on each). 😊

@nicolas-raoul great!, i will try to contribute for the edit feature

[neeldoshii]

@nicolas-raoul I think we should have ticket for App modularization + Jetpack Compose.
@ all Some points for discussion
We should have a plan on how we should get this migration done [each module wise eventual migration], benefits and priority on which module we should migrate first.

2nd. While migration what's our plan? should we move with same legacy ui, or we should go with revamp at some places.

Open for everyone's view and suggestion and points.

[rovertrack]

@neeldoshii how about we go feature wise ( contributions->nearby ...) then widgets wise (Login -> settings->notifications....)
for the legacy UI part that should be decided by the maintainers , although design and architecture improvements is very much needed )

[nicolas-raoul]

@neeldoshii Yes, would you mind creating an issue? 🙂

2nd question would be better answered by @RitikaPahwa4444

[RitikaPahwa4444]

UI revamp is also possible now, given that @psh and @RyukXO-code have expressed interest ✌🏻I just added a comment there: #6633 (comment).

[sivaraam]

2nd. While migration what's our plan? should we move with same legacy ui, or we should go with revamp at some places.

Just a tip about the UI part, it is indeed agreed that it is very helpful to have the UI revamped a bit. But we may want to scope it properly and ensure contirbutors don't try to focus on both and get a sub-par GSoC experience. I mention this as UI changes might involve way too many discussions due to bike shedding (as far as I've observed. If we don't have finalized designs to work on, they'll cause more delays than it may seem at the surface.

If we really plan on taking up UI changes, better if we:

• decide on specific areas which may need changes (corresponds to areas that will be modularized first)
• what those changes are. I mwan like having agreed upon design wireframes
• mention in the description of the phabricator task clearly about this as it primarily looks like a architecture revamp task right now

[RitikaPahwa4444]

Sorry, I missed the context here. I wouldn't suggest a complete UI revamp for this GSoC as it's still something that the community is driving. Nothing has been agreed upon yet. A design system, however, could still be kept in mind while modularizing, and I'd shared my thoughts on that issue.

[sivaraam]

I wouldn't suggest a complete UI revamp for this GSoC as it's still something that the community is driving. Nothing has been agreed upon yet.

I too understood we weren't planning a full revamp. I just wanted to clarify even minor revamps may divert the GSoC project track and was trying to suggest we pick specific ones after choosijg areas that we'll be focusing on.

A design system, however, could still be kept in mind while modularizing,

Agreed.

... and I'd shared my thoughts on that issue.

Just to confirm, do you mean this comment #6633 (comment) ?

[RitikaPahwa4444]

Just to confirm, do you mean this comment

This one: #6392 (comment).

Just for clarity: theme module could be built for the existing UI, so no effort to be put in deciding what looks good :)

[neeldoshii]

Just a tip about the UI part, it is indeed agreed that it is very helpful to have the UI revamped a bit. But we may want to scope it properly and ensure contirbutors don't try to focus on both and get a sub-par GSoC experience.

Agreed. Perhaps we can scope the UI revamp to a specific module or a few screens (like login #6626 (comment) designed by @psh) so contributors can stay focused and have a more structured GSoC experience.

For the login flow specifically, I believe it would be better to go with the revamped UI rather than the existing one, since we would be rewriting it from XML to a declarative Compose-based UI either way.

For other screens, however, we may first need clear wireframes which I believe we don't yet have yet. Hence, it might not be wise to include a broader UI revamp within the GSoC scope this year.

Tagging @sivaraam / @RitikaPahwa4444/ @nicolas-raoul for their inputs.

I think it would be better if we clearly define and prioritize the modules for app modularization under GSoC. Some can be kept as lower priority or “good to have,” so if contributors have bandwidth they can take them up, otherwise they can be skipped to keep the scope manageable.

For prioritization, I believe we should consider areas with higher ANRs, screens where performance improvements are needed, and modules that are more tightly coupled or harder to maintain, so we can focus on changes that have the most impact.