Native Support for Apple Silicon Processors
Phil Gons (Logos)
Administrator, Logos Employee Posts: 3,803 
Please release a version of Logos 9 that runs natively on Apple's new ARM-based M1 processor (and future versions) so we can take advantage of the performance gains without the performance penalty of the Rosetta 2 emulation layer.
We are planning to run natively on Apple Silicon as soon as possible. See our current plans (https://community.logos.com/forums/p/196433/1139418.aspx#1139418) and this this clarification (https://community.logos.com/forums/p/196433/1139481.aspx#1139481).
We are planning to run natively on Apple Silicon as soon as possible. See our current plans (https://community.logos.com/forums/p/196433/1139418.aspx#1139418) and this this clarification (https://community.logos.com/forums/p/196433/1139481.aspx#1139481).
Tagged:
83
Comments
-
Creating a version of Logos to run natively on Apple Silicon processors should be given high priority by Faithlife.0
-
Apple is moving all of their hardware to their own silicon. Logos needs to move with them.0
-
There will be a mass move toward Apple M1 Macs over the next year. Software publishers are quickly optimizing their apps. Many FL customers will move to M1 once major sw publishers like MS and Adobe optimize their apps over the next few months. MS O365 is already in beta for M1 and Adobe has stated they will have both Photoshop and Lightroom Classic optimized somewhere between December and Q121. It would be great to support FL customers with an optimized app quickly instead of waiting until the appropriate number of users are disgruntled before optimizing. Many software publishers are setting a high bar. This is what good businesses do.0
-
Yes, Apple is moving the Mac to Apple Silicon, and Logos needs to run natively on Apple Silicon.0
-
@dan-lioy-83, it is planned and a high priority, but based on our tech stack the two options I outlined here (https://community.logos.com/forums/p/196433/1139418.aspx#1139418) are the fastest paths to native support. The alternatives—rewriting the app and building support into .NET and/or Mono—would take much longer.0
-
@inthehutch-100, we're planning to, which is what this suggestion is marked as planned. The two options I outlined here (https://community.logos.com/forums/p/196433/1139418.aspx#1139418) are the fastest paths to native support. The alternatives—rewriting the app and building support into .NET and/or Mono—would take much longer.0
-
@dvcmikenc-forums-79, we're planning to. It's a matter of *when* not *if.* The two options I outlined here (https://community.logos.com/forums/p/196433/1139418.aspx#1139418) are the fastest paths to native support. The alternatives—rewriting the app and building support into .NET and/or Mono—would take much longer.0
-
@mattspeakes-42, we're moving as quickly as possible, too. The two options I outlined here (https://community.logos.com/forums/p/196433/1139418.aspx#1139418) are the fastest paths to native support. The alternatives—rewriting the app and building support into .NET and/or Mono—would take much longer.0
-
@phil-gons Apple’s commitment to supporting Rosetta 2 seems significantly shorter than the 4–6 year developmental timeline for Logos running natively on Apple Silicon delineated by Phil @ Faithlife. If so, that could prove to be a considerable logistical challenge.0
-
I guess there may be a huge opportunity to leverage the multiplatform features of .net 5 and 6. I'd love it if the same work that goes into native mac produced the side benefit of native linux. I know that Phil has posted about code sharing between platforms before and it seems to benefit everyone in the end.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
You better get started sooner than later because in a couple of years people buying new Macs will not be able to use Logos without this.
Dr. Kevin Purcell, Director of Missions
Brushy Mountain Baptist Association0 -
An urgent and important matter for me and, increasingly, for other Apple users.0
-
@dan-lioy-83, that 4–6 year timeline was for a rewrite, which we're not pursuing. The timeline for Mono or .NET 6 adding support is probably 6–18 mos.0
-
@kapurcell-63, there's really nothing to get started on. It's a waiting game for Mono or .NET to add support. A rewrite isn't a viable option and would take much longer.0
-
@nickstapleton, can you share what matters are urgent? The only issue I'm aware of that we need to address is low frame rates with webviews, which we're actively working on and is unrelated to native support for Apple Silicon.0
-
@phil-gons while most software I’ve installed and use on my MBP M1 work fast, logos is slow especially in Home page, notes, Psalm explorer and a few others.
Dr. Kevin Purcell, Director of Missions
Brushy Mountain Baptist Association0 -
@phil-gons in your other comment you said webviews. Im guessing that’s my biggest issue.
As for waiting in others to fix things that would make her nervous if I owned a biz that was so dependent on a 3rd party. You’ll probably be fine with .net. MS is already being aggressive with Office so hopefully they will be with that too. Aren’t they in charge of it? I don’t know about Mono. Not familiar. If it wasn’t for Logos I probably wouldn’t have ever heard of it.
As an M1 owner if I can help test things I’d be happy to. BDr. Kevin Purcell, Director of Missions
Brushy Mountain Baptist Association0 -
@phil-gons With more users transitioning to Apple Silicon devices, especially as they release more of their Pro models in the coming year, it's important that the Logos user experience not be compromised. Hopefully, it will be optimized sooner rather than later. I know you recognize this, Phil! Simply want to add my voice to express its importance to me.0
-
@phil-gons My new M1 Air arrived today! I must not use those features of Verbum/Logos that some found to be slow; what I use moves along quite well! No one outside of Apple knows, but a good guess would be that Rosetta 2 will be around for a couple of years, at least. I recommend optimizing the current software for M1 now, to address the issues that some have found, and doing whatever you can to get a native M1 app ready to go before Rosetta 2 sails off into the sunset.0
-
I definitely want to see Faithlife prioritize native support for M1 above all other Logos concerns in the Apple sphere.
I have invested a lot of money in Logos and am unlikely to spend any more until Logos 9 runs natively on M1.0 -
I have an Apple M1 Macbook Air, Logos is barely usable on it. The main issue is the notes there is a huge delay while typing. I am really hoping Logos puts out a native version sooner than later. I was also thinking about replacing my desktop with the new Imac's that will launch at the end of the month, they also have the M1 chip. I think considering how many people use Apple products now days that there should be no doubt that creating a native version should be top priority for Logos.0
-
I’m guessing the dev team @logos is probably working as hard as they can. I am hoping that by the end of the year we will have native support. I hope their is an iPad Pro version of the app coming down the pike. Of course, this will largely depend on whether Apple decides to create a version of iPadOS that justifies the specs in the iPad Pro.0
-
@daniel-crackower-94 Have you resolved this issue yet? I just ordered an M1 Mac Mini (16GB 512). I ordered it in part because of all the positive reviews that I have been reading from other logos users. I hope I didn't make a mistake, lol.0
-
Logos is running fine on M1 Rosetta. I don't care how it is done, as long as I can keep on using Logos Bible software on my Mac M10
-
@luuk-dondorp-30 BTW: I am running Logos on a MacBook Air M1.0
-
Yes, I vote for native L9 on Apple Silicon as soon as possible. My iMac is 11 years old (they don't break) and am stuck at OS 13:6 (High Sierra). L8 support has stopped for me. iMac 24 is a perfect solution to get both L9 and Apple OS. I will not go back to a Windows environment, so if the performance with the emulator is all we will get, I may just stay with L8 and my Intel iMac until it breaks---if it ever will!0
-
I would like to see native support for the M1. Just purchased a MacBook Air with M1.0
-
Just to add another use case for supporting native Apple silicone early--I am away from a power source for extended periods of time and not having to run under Rosetta2, should extend battery life.0
-
I have been running Logos 9 on a basic Mac mini for the past ten months. I am planning on purchasing a new MacBook Pro with the M1X in the near future. I would welcome a version of Logos that runs natively on M1. All my other apps now do so.0
-
@phil-gons , do you know if the M1 dev work would include the feature parity support?0
-
With Apple's expected announcement of M1X MacBook Pros at it's Oct 18th event, it would be great to get an updated status and rough timeline for native Apple Silicon support. Appreciate any info that could be shared.0
-
@David Tucker Agreed!0
-
@Charles Gilliland I'm in the same shoes!0
-
Yes please. Especially in light of the anticipated M1X announcement,0
-
Please please please add native support for the M1 chips!0
-
I’m putting all my eggs in the M1 basket!0
-
This article should be a wake-up call: https://appleinsider.com/articles/21/10/28/its-time-to-drop-apps-that-dont-support-apple-silicon-natively0
-
Accordance already runs natively on Apple Silicon. ProPresenter already runs natively on Apple Silicon. I certainly hope that Logos and Proclaim pull off a quality native solution before it is too late.0
-
Last week, I emailed Logos support (tech@faithlife.com), asking for an updated status and rough timeline for native Apple Silicon support. Below is the response I received:
"At this time there are no plans to develop a version of Logos for native M1 support, as this is a very, very small percentage of our user base, we have found that Logos runs effectively through the Rosetta emulator."
Below is my response. I haven't heard back from them yet, but thought it would be helpful to open this up to the Mac Logos community (and hopefully Logos Support) for comment.
"Honestly, this is a very concerning statement by Faithlife that “there are no plans to develop a version of Logos for native M1 support, as this is a very, very small percentage of our user base". Is Faithlife factoring in that Rosetta will not be supported indefinitely and is not a long term solution? Does this mean Faithlife plans to drop support for Mac!?
Also, this is very confusing since this does not align with this multiple posts I’ve seen from Faithlife stating “We are planning to run natively on Apple Silicon as soon as possible." (see this link for reference): https://feedback.faithlife.com/boards/logos-desktop-app/posts/native-support-for-apple-silicon-processors
This article from Apple Insider (which came out today [Oct 28th] highlights concerns Mac users should have regarding apps that don’t have a plan to support Apple Silicon.
https://appleinsider.com/articles/21/10/28/its-time-to-drop-apps-that-dont-support-apple-silicon-natively#P2yL
Given the significant investment I and other Mac uses have made in our Logos libraries, we honestly need assurance from Faithlife that a solid plan is in place to transition Logos to Apple Silicon. Can you please share my concerns with your supervisor? I’d appreciate a followup email from them clarifying Faithlife’s plans."0 -
@Brent Wilson Totally agree. I referenced this article in an email exchange I had with Logos support (see post below). Let's hope Faithlife provides some assurances on a native Apple Silicon version of Logos.0
-
@David Tucker I’m very interested in this. If you get further response would you let us know?0
-
Very interested in this after the most recent MacBook Pro update. I’d love to hear how the plans to provide native support are going. If there is any question that it will happen I’d like to know before investing in a Apple Silicon Mac.0
-
@Jon Varner Yes, I'll be happy to post any updates I receive (or perhaps Faithlife will respond to this thread). Praying it's just a miscommunication from Faithlife support.0
-
We're actively working on it now. It's not a matter of if but when. We're fairly confident we'll have full support with the next major release of Logos.0
-
@Phil Gons (Faithlife) 🎉0
-
The ideal solution, of course, is for Logos/Verbum to have native M1 support. If, in a worst case scenario, this doesn't happen before Apple pulls the plug on Rosetta 2, we have an alternative. Get Parallels Desktop 17 and set up a virtual machine for Windows 11 ARM, and install Logos in Windows 11. So far, Microsoft is not (to my knowledge) giving a time limit for Intel emulation on Windows 11 ARM. Yes, it would be emulation inside a virtual machine, but it would be better than no Logos on Mac!
I have Parallels and Windows 11 ARM on my M1 MacBook Air and I am surprised by how well Windows 11 ARM works in this scenario. The process for setting this up is a bit involved, but if you like this sort of thing, you'll enjoy it!0 -
@Mark Nolette While this approach may work (depending on what Windows allows as far as Windows on ARM, it is not a simple solution for the average Logos user on Mac.0
-
@David Tucker Yeah, that had better just have been a miscommunication from Faithlife. A choice to not natively support Apple Silicon is essentially a choice to no longer support Mac within the next couple years or so (depending on how soon Apple pulls the plug on Rosetta 2).0
-
@Phil Gons (Faithlife) Thank you Phil. Very glad to hear a solid plan is in place! I'll be praying for smooth progress and God's speed in completing this work!0
-
.NET 6 will be releasing on 9th November.
https://www.dotnetconf.net/0
