this post was submitted on 12 May 2022
14 points (100.0% liked)
Open Source
31066 readers
465 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
First decide on a platform, then language. Do you want to make a windows gui client? Apple? Mobile? Web? *nix console?
GUI is the hardest part of programming on pretty much any platform, especially compared to how simple XMPP is.
Javascript/web is probably easiest for a beginner...
You're right, I'd like to develop for android, and I prefer to learn something else than JavaScript. Thanks for the answer and the info of course :)
In Android land Java is the go-to language. But there's already an abundance of XMPP clients on Android. Do you have ideas for specific features you would like to develop in particular that you could not find in an existing client?
I will think about java, thanks :). Clients I used (conversations and forks) usually lacks a lot of the visual "hints" presents in other applications. E.g. there is no way to answer to a specific message, there is no way to "pin" messages, different messages from the same person aren't easy to identify, overall experience is not great compared to modern instant messaging apps like WhatsApp/signal and can be frustrating... there are a lot of things that I would love to see, but I understand that they will not magically appear if no one will work on them
There are some underlaying reasons why some of these features do not exist, it is not (only) because the client developers do not want to implement them.
I think this could be done even on client side, at least I have some ideas (e.g. "pinned" messages could be just messages with a "room" tag locally saved on the device and chronologically ordered; answering a message can be implemented with markdown and a local search for the message when tapped on it). Of course I have absolutely no idea how hard it could be :D
I am no Android developer but apparently you can use Kotlin for that:
https://developer.android.com/kotlin/
Yep, I thought about Kotlin, maybe if I can learn that I could help jerboa development too :D