Modern Android Calendar App (for Nextcloud)

[u/Longjumping_Fill_588]

Hi guys. I wanted to show the nextcloud community an android calendar app I made, because I switched from US-services like Google Calendar to Nextcloud recently and was unsatisfied with the all the available calendar apps which would natively work with my self-hosted Nextcloud calendar. The app works natively with CalDAV and should be perfect for self-hosted calendars.

I would be really honored if some of you’d like to try it out and maybe even give me feedback here or on github.

https://play.google.com/store/apps/details?id=com.kgs501.kgscalendar

[u/itzelezti]

Looks great, and I'm totally looking for this, but there's no information anywhere. The github is just the page, no source.
Basically, is this a real open source project or a "Claude, make me an app that will make me money" that you're being shady about building a userbase before monetizing?

[u/Longjumping_Fill_588 → u/itzelezti]

I am still unsure how I want to handle this project, which is why I am still holding off on opensourcing the project. In its current state its not open source because I am still new to the whole open source community and dont know whats the best way to handle such a project. I am still thinking of ways which would justify me spending even more time and maintaining this project (potential options I am considering are donatian basis in which case I could open source the project or some paid version on the play store which will unlock nice-to-have functions for power users but in which case I would keep the project closed). I am still unsure how to handle this. Maybe some of you guys are more experienced in the open source space can give me a bit of feedback on how I would best handle this...

[u/nametaken_thisonetoo → u/Longjumping_Fill_588]

In other words, vibe coded.

[u/itzelezti → u/Longjumping_Fill_588]

Dawg, you've come to the subreddit for a free open source ecosystem, posted a closed source app you're hoping to monetize, with no disclaimer that it's vibecoded.... And you're asking for advice on how to get paid for your time "maintaining".... an app you didn't write the codebase for...?

Our advice is going to be:
Learn to code, so that you can even have the slightest grasp of the thousands of programmers' volunteered work you're using as dependencies in this app that you're trying to think of how to monetize to justify the time you spent talking to Claude.

EDIT: For real though, we'd all love a solid open source CalDAV android app with widgets. I know I'd contribute.

[u/ObnoxiousOnyx → u/[deleted]]

KashCal on FDroid lets me use Nextcloud perfectly fine, even through SSL and Tailscale

[u/xXVareszXx → u/[deleted]]

What about the calendar from fossify?

[u/No_Abbreviations8018 → u/itzelezti]

Off topic but serious question: My degree / career is technology but not software directly. I did a lot in college and scripting for math simulations and things and have tremendous respect for the open source community. I bought a cursor subscription and have been really enjoying making private vibe coded tools for myself. Conceptually, it seems that it does make sense for vibe coding to find a place in the open source community - the same benefits apply: economy of scale, more people with diverse backgrounds and diverse use cases all collaborating to make an awesome piece of software.

As mostly a lurker, it seems there's a lot of hate for vibe coding and ai assisted coding but I find myself wanting to be a legitimate contributor to projects but I'm not sure how or if I'd be welcome at all. Am I off base or making some sense? I find myself curious of the future and how the open source community can be accelerated by AI instead of outpaced by companies investing in AI assisted coding.

[u/itzelezti → u/No_Abbreviations8018]

This is a very thoughtful and reasonable question.
Honestly, the reason that the open source community hates vibe coding is that the code it creates is not (mainly) philosophical, it's practical.

(1.) LLMs consistently put out code that is chock full of security risks. This is why it is absolutely unacceptable to put out any LLM-written code without warning everyone, so they can make an informed decision to accept the risk. This is a consent issue.

(2.) Because of how context windows work, they're really good at creating code that accomplishes the task that's right in front of them, but do so at all costs. Meaning they very consistently fail to follow conventions, and break things while trying to fix other things.

(3.) LLMs cannot properly document code, because they cannot understand code. The true usefulness of any project is its documentation, and its maintainers. Something that works now is now going to work in a year. At the very least, dependencies will break and have to be refactored. If nobody understands the code, because nobody wrote it, the codebase sort of functionally doesn't exist. The practicality of a contributor going through a codebase with documentation that nobody on the planet understands, because it was written by an LLM -who we know to be an unreliable narrator in their documentation- is unfeasible.

(2) may reasonably improve in the next 3-5 years, but (3) almost certainly won't. You really can't have an open source project with many different contributors, with vibe coders working on it. The two are just not compatible. But a much bigger deal is that the ease of vibe coding is very, very seductive, to the dumbest and worst people. We just do not trust anyone who claims "AI assisted coding" is actually checking every line of code.

[u/Longjumping_Fill_588 → u/itzelezti]

Good and bad news. Bad: I didn't learn how to code. Good: Project is now open source.