macOS desktop client


#1

Where is macOS client, hope you can release beta or something soon!?


#2

+1 !
When do you think the mac os client will be released?

I’m in to be a beta tester if you like.

Thanks


#3

The MacOS desktop client release has been delayed. We will definitely announce once we have something to beta, but it looks like it could still be a few months away.

Just in case there are new folks that are not aware, we also have an odrive1 Mac desktop client that may satisfy your use case until the odrive2 Mac client is ready: https://docs.odrive.com/docs


#4

A post was split to a new topic: Odrive2 subscription credit for odrive1


#5

I signed up for the Odrive2 subscription using the credits however I did not realize that there was not an Odrive2 for Mac yet so does that mean I really don’t have Odrive2 as of yet? When do you expect the Mac version to be released?

Are there any visuals as to how it will all “look” it would be good to familiarize myself with the platform before it arrives so we can see if it will be beneficial.


#6

Hi @foster,
The Mac desktop client is still a few months away.

The look of it will be similar to the Windows desktop client, but more MacOS-y. Take a look at this post for info, screenshots, and videos of the Windows desktop client:

Also keep in mind that we have an odrive2 web client, Android client, and iOS client, which you may find useful.


#7

hi @Tony, until macOS client for odrive2 is ready the idea of odrive2 is not usable for me. I will patiently wait for this while renewing the subscription for odrive1 in November - unless you provide the client until then


#8

Is there an update on when the MacOS client will be out?


#9

Still anxiously awaiting any beta for this on MacOS. It doesn’t have to be perfect, and I do provide feedback when I beta test stuff! :slight_smile:


#10

It’s been a few months since you said it was a few months away. :slight_smile:

I’m now premium, so chop-chop guys, lots of other options out there kind of suck.


#11

Hi @sporkmanodrive,
Unfortunately I don’t have any new information to report. Are you currently using the odrive1 MacOS client?


#12

I’m using odrive1…

But I’m probably asking it to do more than it can. I keep work projects in the cloud, and then archive them there when I’m done. Lots of wordpress, so easily many thousands of files per project, and I tend to keep some client backups in there as well. I recall in some odrive1 help topics there was talk that at some point we can just end up with more files than odrive can keep track of. I’m hoping odrive2 is more clever about that (like copying other clients and using kernel hooks to check for file mods).

And with B2’s pricing, I’m looking to throw even more stuff in the cloud.

And for collaboration and such, being able to tie in 6 or 7 other various cloud providers in one place is very handy. I really want a client that rolls everything together and performs well…


#13

Hi @sporkmanodrive,
Thanks for the follow-up!

I think any client will end up in a situation where there data that needs to be tracked creates enough overhead that it impacts the user experience in a significant way.

odrive2’s approach can lend itself to driving a more “targeted” setup for data sync and it has the Explorer app to provide an interface for accessing remote data without needing to sync. I think this will naturally create configurations that lessen the scope of data that is synced on the local system. But, even in odrive2, if you want to have the client track/sync millions of objects it can also end up in a situation where the overhead of all of that tracking becomes impactful.

odrive1 actually uses filesystem events (when supported by the OS) as notifications of local changes. This is how it is able to react to local changes quickly and start those uploads. It also does a “just in case” background local scan, periodically. These scans are usually completed fairly quickly, even with lots of local objects, unless “local” is actually on a networked drive, or a slower external drive.

General overhead is ultimately a case of total objects, but the impact is more the remote tracking vs the local tracking. For example, a traditional backup client would have much less overhead since it really only needs to track the local changes and push those up.

Since odrive1 is syncing, it is worrying about both sides, and that requires a lot more work. The best way to ensure snappy behavior is to collapse structures (unsync folders) that are not needed on the local side. Since you mentioned that you archive a lot of things, unsyncing those areas is the best bet for improving performance.

We also recently tweaked some of the odrive1 scanning internals to try to reduce the amount of work it is doing, which eases some of the overhead pressure for large-scale data.

If you are collapsing local areas with odrive1 and still encountering issues with your data, can you direct message me on the odrive1 forum and we can see if there is anything else we can do improve the experience?