❔ Guidance with developing a messaging application
So a friend of mine and I recently decided that we'd like to make a desktop messaging app for two main reasons: to start and complete a more advanced project and to prepare for our examined coding application come summer 2024. However, I would like some insight and advice before we proceed.
In essence, the messaging app will allow users to talk in 1 to 1 DMs or join a group/server. They will need to create an account using an email. As for the GUI, I know a small amount of WPF but we wouldn't mind learning or using something else instead. That's pretty much all that's set in stone right now
We're still looking at how the logic regarding how messages will be sent and saved will work and how creating an account with an email will work ( checking if an account exists and then loading all of said accounts relevant data)
I would appreciate any and all advice regarding this project, such as what order would it be best to approach this task, what libraries would be most suitable and what sort of features you would personally want implemented in a messaging app.
Links to any resources such as videos/discussions/blogs would also be incredibly helpful
18 Replies
my humble opinion is that to understand what advices to give i would like to understand how much advanced you wish this project to be
like a simple exe that does ui/networking/storing, or a full fledged service with tiered architecture, modularity, event store, websockets, text search, multimedia, and so on
or something in between, i guess
anyway you could start reading about these kinds of protocol to start having an idea of what features you'd like, like the irc rfc or xmpp
I recommend using .NET MAUI
Sadly .NET MAUI is best mobile support we've got and it's absolutely dogwater
We’re pretty happy with it, been able to put out a couple of apps for clients which they’ve liked
We want the app to be on more of the simpler side
then go for a simple server/client split
Mind explaining in more detail? Only have a vague idea
i guess that means like <100 users
Yh, just him and I and then a few extra users from wherever who can give some feedback
I also wanted to ask : when my friend and I are making this app, should it be built under one solution with multiple projects?
Up until now I've mainly made applications with a single project
Sure, that makes sense. Also, use git and github/gitlab/bitbucket to share your code
so you can work on it at the same time
Yh, I've set that up already and familiarised myself with pushing/pulling etc
Since this will likely take my friend and I a while, should I simply refer back to this thread when I need some guidance or make a new thread if it's been a while?
Threads only stay alive for 48 hours of inactivity
So if it's longer than that, new threy
Thread
Would any of you happen to know of any youtube videos/tutorials which are relevant to this case?
The ones that I have found are outdated or they aren't intended for the same purpose
probably just trying to do it and facing the challenges is more useful than a tutorial
i mean you read a tutorial about specific techniques like architecture, or about a specific package
then the rest you learn by doing
Yh, that's the probably for the best
I've been having this issue where when I maximise the window, certain elements aren't resized properly :
BlazeBin - rnzlftiifbuw
A tool for sharing your source code with the world!
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.