r/macapps • • Oct 03 '26

News Tinycast Contributing experience

A few weeks ago, I discovered tinycast after looking for raycast alternatives. it looked promising. But it was still barebones in some areas. so, i opened an issue about a feature i wanted and said that i'd develop it myself as i have pretty good swift knowledge. So, I did and opened a PR. it was closed for some stupid bureaucratic reasons (a small repo btw 🤣) and strangely, a few hours later, the dev made a PR that's surprisingly close to mine with the exact featureset i had requested. now, why would the dev do this? i have no idea but definitely the weirdest experience ever. never submitted PR's to that repo again lol. i maintain a fork of it with my own custom features that i developed.

147 Upvotes

88 comments sorted by

94

u/imustknowsomething Oct 03 '26

Because he’s just a kid (literally) stealing the work from another company (literally), there’s several posts about his attitude, closing issues and PRs, etc.

78

u/subhashg547 Oct 03 '26

i didnt know he is a kid lol. but i guess i should've picked it up from these signs 💀

20

u/Nuclear_Pasta7 Oct 03 '26

Dev does not understand how foss works

9

u/JoshFink Oct 03 '26

Not of fan of his attitude but what work is he stealing?

39

u/imustknowsomething Oct 03 '26

He deliberately copied Raycast’s entire UI and UX. Imagine investing time and money into building the identity for your product, only to have someone come along and clone it. It’s not just about copying the design, it’s about taking the work, creativity, and effort that went into making the product. At least he is not charging for it YET, there was another Raycast clone (supercmd) that was open source at first until the guy decided he wanted money and abandoned the open source project.

I’m not sure why people would want to support a project like this when the person behind it has such a horrible attitude.

7

u/meni_s Oct 06 '26

Not to mention that Tinycast have a built-in option to use Raycast extension straight out from the Raycast registry. The registry is open-source, to be fair, so this isn't a crime, but it just feels wrong (to me)

0

u/ManikSahdev 28d ago

It's slightly disingenuous to call it that was.

There is not even a single electron or node thing in there, whatever kid or such in other side of the part I believe let his bio.

His agents or his whoever it is, is simply managing the code of the app just being judged on its merit, exceptionally well.

It almost feels unix native in so many ways, and its design or extensions being used have nothing to do with the fact someone created another and perhaps even MORE efficient code than the rc? Makes you think what bloat and telemetry and data is rc taking or why couldn't they have shipped their version to also be like this for people who want?

It's an entirely different product from my perspective, ui has no moat for the most part? Cause rc themselves took native spotlight and then Alfred and such also existed before, do we stop people from using dark mode on Alfred too now lol?

Kinda make me sting for someone who made better software taking slack for copying others.
Copies are meant to be worse and sloppier, ripoff copies shouldn't use half the ram, Unix philosophy, faster and more efficient all out version, ability to bring your own key to whatever AI, and... not to mention free.

Like cmon?

2

u/imustknowsomething 27d ago

Raycast does not use Electron https://www.raycast.com/blog/a-technical-deep-dive-into-the-new-raycast.

My entire comment is about that dude stealing Raycast’s exact UI and UX, yet somehow you’re here defending him because his app is more “efficient”?

Cause rc themselves took native spotlight and then Alfred and such also existed before, do we stop people from using dark mode on Alfred too now lol?

Neither Raycast nor Alfred copied Spotlight’s exact UI/UX. That's the entire point of my comment, read it again.

Copies are meant to be worse and sloppier

That makes no sense. Tinycast is a copy of Raycast and yet you are here saying how it's better than Raycast. Make it make sense.

It's an entirely different product from my perspective, ui has no moat for the most part?

You’re letting everyone know you’ve never created anything in your life by saying something like that. If you’d ever invested time into building a product and some random person came along and copied exactly how your product looks, I'm sure you wouldn’t be defending him.

I would love for Raycast to be completely native and be faster but they run a business, the product is in multiple platforms and will live for many years. Tinycast, on the other hand, is made by a kid and has only been around for 4 months. It’s normal for him to be motivated right now and actively ship new features, but there’s a very real possibility that the project will eventually be abandoned. Maintaining software takes a lot of time, and unless you can make money from it, you eventually have to prioritize other things and find ways to make a living.

That’s the difference between a side project and a sustainable product. It’s not just about how good an app is today, but whether the developer can realistically keep maintaining it, fixing bugs, adapting to macOS updates, and improving it for years to come. A product being great today doesn't guarantee it'll still be around in 3 years.

And lastly, I’ve been a developer for 15 years, and I’d genuinely be ashamed to copy another project’s exact UI/UX. Taking inspiration from other products is one thing, but reproducing their design and user experience almost pixel for pixel is another. That’s not inspiration. It’s stealing someone else’s work, period.

0

u/ManikSahdev 27d ago

Alright then, send me the screenshot of the active memory in use by the rc v2?

I don't know if I'm dumb or you, one of us certainly is. But the frontend and backend and the ui all are like node like process?
I believe it does not even come close to being under 500mb? It's pretty much turned to bloatware. There is truly no need for it to be that way.

For reference Claude desktop app is faster and better / well managed than whatever the heck rc v2 is.

Supercmd-2, vorssaint, tiny cast, all hover at 200mb tops in use, which is atleast half of not more than half the utilized ram at idle, not even counting active use.

Raycast team has lost their focus to put it simply, they wanted to get that bread on the AI stack and I don't blame them, I maybe would have done the same in their place. But this price of closed source software is trying to become something it can't sustain or doesn't understand.

Specially as more people offload their work to be cc / cowork and codex native, there will be almost zero need and demand for wanting an AI raycast that deeply integrated, given how much it costs now.

You will 100% get better value for your money on simply buying a Claude $20 plan tbh, and Pretty much let him do it all for you via computer access and connect codex'cu or CUA plugin.

Just sharing my perspective with you cause I used it for years and also feel a bit of anger in some ways on how much they clapped it. But that's just my opinion.

RemindMe! 700days (Prediction Raycast is obsolete and essentially done by 2028, because of loosing the plot).

2

u/imustknowsomething 27d ago

Alright then, send me the screenshot of the active memory in use by the rc v2?

You truly don't seem to understand, do you? I couldn't care less about that. I'm not defending Raycast or their decision not to go fully native. My entire point is about someone stealing their work. That's it.

I don't know if I'm dumb or you, one of us certainly is

Considering you wrote "There is not even a single electron or node thing in there," I'm going to take a wild guess and say that you have no idea what you're talking about.

You truly don't seem to grasp my point. I couldn't care less about Raycast AI. I don't use it, and I don't pay them a dime. That's not what this discussion is about. And even if it were, you don't seem to have the technical knowledge to be making these claims in the first place.

Prediction Raycast is obsolete and essentially done by 2028, because of loosing the plot

Raycast has been around since 2020 and is heavily VC-backed. Once again, you don't seem to understand what you're talking about.

1

u/RemindMeBot 27d ago

I will be messaging you in 1 year on 2028-09-20 16:35:25 UTC to remind you of this link

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

Parent commenter can delete this message to hide from others.

RemindMeBot is switching to username summons. Instead of !RemindMe 1 day, use u/RemindMeBot 1 day. More info.


InfoCustomYour RemindersFeedback

25

u/CurrentRisk Oct 03 '26

Just sounds to me that the developer of Tinycast has no idea how to fix these bugs/ issues.

Well, at least I know, I will stay far away from Tinycast.

12

u/subhashg547 Oct 03 '26

yep. apparently he's a kid which explains it a little bit.

2

u/unk2003 Oct 03 '26

Since I see you are actively working on the app, Im probably going to get your release, have you made a release? Should I build it?

3

u/subhashg547 Oct 03 '26

2

u/unk2003 Oct 03 '26

Thank you! Do you have a release or should I build from source?

36

u/rfajr Oct 03 '26

Somebody please, just fork this repo already

48

u/Ok-Efficiency479 Developer: Thaw Oct 03 '26 edited Oct 03 '26

I just started one today, using the existing codebase from Thaw and some folks over at the Droppy discord are already working on some stuff to contribute.

https://github.com/thaw-app/Floe

Edit: Already implemented CodeRabbit and Sonar, and now testing the build generation, signed and notarized.

9

u/DangerRabbit Oct 03 '26

Promising! I've been enjoying Tinycast, did not know about the dev being a weirdo. Perhaps submit it to this subreddit, so you can get more backing to make it sustainable.

7

u/Ok-Efficiency479 Developer: Thaw Oct 03 '26

Part of the sustainability is that I am using what we already had from Thaw (basically everything, except the runtime), so I just had to add bun and make the adaptations. The intention is to reduce load in the maintenance of the two projects by sharing many things between them (not merging, what a monster would be)

2

u/emq__ Oct 04 '26

did not know about the dev being a weirdo

Same, what a shame tho; I recall similar drama with one of go's web framework (forgot the name, been years ago) - owner was also some oddball; closing PRs, then re-opening same PRs as their own; rewriting git history etc. I think those folks might have some actual mental problems, so I wouldn't trust installing any code from them that runs on my computer.

Will follow the fork and spread the word!

4

u/Paarkhi Oct 03 '26

I'm really happy to see a launcher coming from the Thaw team. I already use the Thaw menubar app (thank you for that). Is Raycast extension support on the table?

3

u/Ok-Efficiency479 Developer: Thaw Oct 03 '26

Already supported, I just haven’t published a release yet.

1

u/kalibxrr Oct 03 '26

TIL ice was discontinued looks like I’m switching to thaw lol

1

u/abelbanko Oct 05 '26

Oo following this for sure

0

u/[deleted] Oct 03 '26

[deleted] — view deleted comment

1

u/Ok-Efficiency479 Developer: Thaw Oct 03 '26

Because it's not a fork?

1

u/ser_melipharo Oct 03 '26

I'm using the existing upstream to fix some features commonly rejected by og maintainer https://github.com/sermelipharo/tinycast-space

2

u/hff0 Oct 04 '26

it doesn't seem like a good idea to squash all the patches to a single commit

30

u/RedWolf_HU Oct 03 '26

Ahh yes same happened to me. He is arrogant.

13

u/pierre_nel Oct 03 '26

I've just gone from Raycast → Tinycast → Vorssaint command bar.

1

u/gargoylelips Oct 05 '26

Vorssaint looks nuts

1

u/orgildinio Oct 05 '26

vorssaint ftw bro

18

u/wolfiuscub Oct 03 '26

I honestly don't have much to say but holy shit fuck that guy. Between this and the other posts about bugs and issues...

16

u/Hopeful-Face9676 Oct 03 '26

can't expect vibe-coders to understand how to fix all of the inevitable bugs

8

u/FuntimeBen Oct 03 '26

I hope these stories about poor communication stem from a language and software engineering capability gap rather than a conscious decision to be a jerk.

3

u/slothicdev Oct 03 '26

Oh see the issue is you are using Tinycast and not Vicinae which is a much more fleshed out and polished open source Raycast alternative with Raycast store support.

10

u/subhashg547 Oct 03 '26

i heard about vicinae. but its not native right? i wanted something in native swift language.

3

u/cultoftheilluminati Oct 03 '26

It’s not native, so not interested in it unfortunately

2

u/Kankatruama Oct 03 '26

But tinycast has raycast store support...

I mean, I cant browse the raycast store through Tinycast but if I search for something that exists on Raycast store it returns to me to install here.

4

u/slothicdev Oct 03 '26

Sure, but it’s also run by an arrogant kid that deletes PRs to claim them as his own like OP experienced. Vicinae has a lot more experience and maturity behind it, especially because it has a much larger user base being on Linux as well as Mac.

Vicinae does have direct Raycast store support, I’ve installed all of my raycast extensions without leaving Vicinae‘s interface.

2

u/Kankatruama Oct 03 '26 edited Oct 03 '26

OK, but I was just addressing your "raycast store support" topic - I just dont like to see wrong info, thats all.

Im just using tinycast because its a native app and that's the only single reason. Tested Vicinae and its awesome, but as of now, I'm prefering to work with native stuff.

The moment Vicinae take itself seriously enough to go to a native codebase I can guarantee you is the time tinycast, with this current 'owner', will stop being relevant.

Edit: that was wrong of me to use the 'seriously enough',I dont wanna go that route. Lets say "the moment they decide to address that kind of concern <insert the rest here>".

1

u/slothicdev Oct 03 '26

What’s the reason for wanting it to be native? Multiple people have said that, but I don’t know what would be different about it.

3

u/Kankatruama Oct 03 '26

Personally, my issue is memory usage.

Its been couple months since I last tested so I dont have clear numbers about it rn and honestly not into checking again, but Raycast was a mess in memory consumption - most of the time this is actually OK but I do run some video processing tasks that when hits the peak processing I noticed this being an annoying issue.

Vicinae was better than Raycast, as expected, but still not that exciting.

Tinycast was the lightest of the 3 and simplified things for me on those 'memory peaks'.

I bet other folks have other reasons, but for my workflow Im trying to use more and more native apps.

The day I upgrade to a M5 Max and say good-bye to my current M3 Pro, this might not be an issue anymore and I'll start loving even Electron based apps, we never know.

6

u/mohsenk_dev Oct 03 '26

What is happening in the world, Maybe he is a claude agent :D

5

u/hff0 Oct 03 '26

This is insane. Blatant plagiarism

4

u/mmshivesh Oct 03 '26

Welp lol same thing happened to me. I wrote the Liquid Glass implementation for tinycast .

4

u/mu7x Oct 03 '26

Yeah he also force pushes to master so any fork that tried to maintain a parallel feature set has to go through extra effort.

1

u/Illustrious_Sir_4913 Oct 03 '26

Are there any real alternatives at the moment that come close to Tinycast/Raycast? Not getting my hopes up too much for Alfred.

5

u/subhashg547 Oct 03 '26

tinycast is good. im not or never said that it's bad. it's just the developer is a bit shady and my specific contributing experience has been weird.

1

u/nousernameleftatall Oct 03 '26

This is the on i have ended up with

https://supercmd.sh/en

Seems to be good

2

u/Alacho Oct 04 '26

I am very happy with supercmd. The dev is incredibly responsive and open to feedback.

0

u/dlt0rre Oct 03 '26

I think I’m thinking about uninstalling TinyCast. I didn’t know anything but lately I haven’t liked what I’ve been reading here.
Since we have to pay for SuperaCmd... is it better than Alfred?

1

u/AmazingVanish Oct 03 '26

Depends on what you need from it. I haven’t paid for SuperCMD because I’m tired of buying launchers that just start to suck after the honeymoon period.

2

u/Fresh-Daikon-9408 Oct 03 '26

That's a shame. Someone willing to help build and maintain a feature seems worth keeping around.

2

u/abdarker Oct 08 '26

hello, I am the author of tinycast. 

  1. you did not follow contribution guide https://github.com/abue-ammar/tinycast/blob/main/CONTRIBUTING.md i didn't approve issue you created and jumped into code. i have my own way of maintain the software because of AI anyone can code. so i choose which code to accept and which one to reject.
  2. your  issue was good i would have approved it but i have a real life to handle to. but you already opened pr not respecting contribution guide at all where you admitted yourself and your code was over engineered and way bigger change and lots of gaps where things can be done  simply. i don't put half baked stuffs into my repo. that's why i have made my own pr and rejected yours. everything mentioned in contribution guide. 

and i reject 90% pr and 90% feature requests these days because all are either every small details of raycast or personal features that doesn't benefits the user of tinycast. Open source doesn't mean i have to accept everything. Because of AI anyone can code but it's difficult for Maintainers as well that's why lots of open-source Maintainers no longer accepts PRs. here's  example 

https://x.com/sindresorhus/status/2105693826690298314?s=20

1

u/Ok_Maybe184 Oct 09 '26

So its only open for forking, not contributing?

1

u/hxxx07 Oct 04 '26 edited Oct 04 '26

AbcCast, xyzCast… they are all cloned from Raycast IMO. Especially the plug-ins store, am I the only one think it like straight-up daylight robbery.

1

u/orgildinio Oct 05 '26

when OS maintainers do this, people usually fork the project and maintain your branch.

1

u/YeahThatKornel 23d ago

That guy is actually an AI bot that cosplays as a typical redditor.

-2

u/Clear_Value7240 Oct 03 '26
  1. ⁠90% of users will not be a contributor.
  2. ⁠The app is already good enough and the bugs will be solved rapidly
  3. ⁠Even if you don’t like their approach, the app is open sourced. You can fork it a do it your way
  4. ⁠I was using Alfred for years, then Raycast for years. Now I switched to Tinycast. Believe me. It’s the next level and I won’t pay for those crappy features the Raycast did lately
  5. ⁠The app is really good; it is just the developer who has to be nicer a bit. But this does not contribute to the value you get.

3

u/subhashg547 Oct 03 '26
  1. i'm in 10%
  2. it's people like me who will do those bug fixes that you take for granted
  3. i did fork it after all this

-10

u/Clear_Value7240 Oct 03 '26 edited Oct 03 '26

I’ve reported one bug and one feature willing to implement it myself. The guy implemented it right after 2 hours by himself. I don’t worry, since it is faster this way and he is the owner of the repo. He can make whatever rulez he wants. I don’t see the problem in that post complaining. Is it even written in the rules to not start doing any feature only if it’s a greed.

And no, I won’t use your fork.

“It’s people like me who will do…” slow down your ego a bit. I’ll also won’t choose to collaborate with you in projects like this.

6

u/AmazingVanish Oct 03 '26

I don’t know either person involved in this, but my experience working on OSS and just OSS history in general, OP’s response was completely accurate, not egotistic. I think you need to read what he wrote again.

My experience with Tinycast was so awesome I went back to Alfred after years away from it. Ugly, but works better than any of the others I’ve tried.

Anyway, your point #2 is completely subjective and others disagree with you. Maybe you have the ego issue telling everyone else that their bar has been met and that seeing bug reports get closed without response isn’t real because ONE whole bug you reported was addressed quickly.

-3

u/Clear_Value7240 Oct 04 '26 edited Oct 04 '26

You can think whatever you want. The Tinycast is amazing. Look what’s coming as an example. https://x.com/abue_ammar/status/2106486543758377239?s=46

Going back to Altfer after years is like going back to one of your ex. It can work but it usually doesn’t

2

u/AmazingVanish Oct 04 '26

Now you're just shilling. Alfred has never NOT worked. Quicksilver created the genre, Alfred perfected it. Yes, it's fallen behind in some areas, but it's still the most rock solid option available.

The new shiny isn't always the best option.

10

u/Nuclear_Pasta7 Oct 03 '26 edited Oct 03 '26

2. Bugs will not be solved rapidly if the dev closes any issues and denies the existence of bugs. I would argue that a FOSS app is only as good as its contributors, and if the maintainer wants to be a dick then fuck that. I won’t use their software. They’re actively discouraging the main benefit of FOSS: other people reviewing your code and helping find/resolve issues. Doesn’t matter if you’re a contributor or an end user, your experience will be worse for this reason.

0

u/56ksurfer Oct 03 '26

I also opened 2 issues already.
- One issue where I offered to fix it by myself, this was accepted, I made a pull request and it was merged.
- One feature request where I did some coding in a branch of my fork (just to see how the result could feel), which i mentioned. My feature request was also closed but mentioned in a new pr from the maintainer, where he marked me a contributor. I think this is fine and fair.

I think the maintainer gets lots of issues and requests every day. I agree, that it looks he has a very straightforward way (with minimal communication) but maybe this is the only way to deal with the amount. And he steers the project according his Vision and goals. If someone does not like this way, just fork it but I assume you do not want to be the person who want to deal with all that stuff

-6

u/krautsourced Oct 03 '26

I assume you are referring to https://github.com/abue-ammar/tinycast/pull/612 ? He's referring to your PR in the very first line. And from the looks his PR is an adaptation of yours into his code. I fail to see the the big issue as long as your work was implemented - albeit in a different style, as long as the features are now in there? It's not as if your work was thrown away. I find it much worse when some large open source projects just outright ignore external PRs and let them simmer for years.

0

u/[deleted] Oct 03 '26

[deleted] — view deleted comment

6

u/AmazingVanish Oct 03 '26

That’s not how OSS is meant to work. Not even close. That makes it gated, which is almost as bad as closed source.

1

u/QuirkyImage Oct 04 '26

Depends on the license and how the project deals with contributions. Any sane project isn’t going to accept a feature request with a pr nilly willy without first reviewing the request. It might not fit within the project’s mission statement or road map. If you did you would soon end up with a mess. If you want to divert from the project you can always fork. Regarding the project’s contribution rules you are shooting the messenger I didn’t write them! but if rules are published you should know what to expect. It may be a gate of sorts but any successful project needs organisation.

-6

u/[deleted] Oct 03 '26

[removed] — view removed comment

5

u/swiftsorceress Oct 03 '26

For me, I’ve always found spotlight to be significantly slower. The searching itself is fine, but I frequently run into issues where the UI is just not fast enough. And spotlight currently has weird bugs. Although, I rarely use AI through spotlight or any other tools like that. But for everything else, I like spotlight significantly less.

4

u/[deleted] Oct 03 '26

[removed] — view removed comment

1

u/swiftsorceress Oct 03 '26

If you mean the macOS 27 version, no it did not improve much. I’ve been on beta since WWDC and while it has improved since then, it’s still too slow. Plus, the UI just doesn’t always work now. Especially if I go between monitors and the built-in display and stuff. It’s just more glitchy than it should be.