mergeconflict229-1
James: [00:00:00] Frank it is officially happened. We can run iOS applications on Macko ass because these new M one chips apparently are the best thing ever created. Ever I'm looking at all the reviews, Frank, I'm looking at all the, the verge articles. I'm looking at all the YouTubes. And everyone said that these are the best laptops ever created in the entire world.
Frank: [00:00:31] A fact, yeah, that seems to be the truth. As far as what Twitter has told me, I only know what Twitter has told me because you and I have DD Ks, and then they're not the fastest. Fastest bury in the bunch that analogy doesn't work. Um, but, uh, I didn't order one. Did you order one? 
James: [00:00:52] We talked about this a little bit last week.
I really am now thinking about it because I was watching Dieter over at the verge and. He was reviewing the Mac book air. And he said that this puppy just completely flies. He could not, he could not distinguish an x86 application from a native compile application. 
Frank: [00:01:14] Yeah. So we've said before that Rosetta two is kind of impressively good.
And that was just from us running on the old hardware. And so seeing these, uh, uh, reviews, whatever performance things come out, it's all just kind of validating kind of, I think how we felt was. Dang, this thing actually works and it works really well. So we are in that scary space where I don't know what we got this hardware, but somehow I was still just kind of putting it off in my head a little bit because I'm working on other things.
I'm always working on something else. It seems. And I was like, Oh, Apple's going to take its time with, uh, rolling out this hardware, you know, I have months and months to wait. And then they just started selling max it's out there. You can buy one today and I'm like, Oh, jeepers. Oh, jeepers. Uh, I need to catch up and really think through what I'm going to do with my apps now and going into the future.
James: [00:02:17] Yeah, that's a good point. There's um, Very different strategies. And that's what I want to talk about today. As we talk about our apps that are in the store for iOS today and for iPad. Awesome. What we're going to do here. But I think it is very fascinating because yeah, you're right. You know, I also was in the same campus.
You, we had the DTK as we still do, those are running. A 12 Z modified ship of some sort is not the M one chip. I double-check the specifications on the box. When I was wrapping mine up. I can't upgrade mine. So I don't make literally waiting for you Frank, to do the upgrade and test my apps for me, the VA screen-share session.
So I'm really waiting for this one day two for it to happen. We, we, we, we can do a streaming live that could be entertaining because it's out right. It's out into the world and I'm assuming. That things are going to run amazing based on, you know, what they've said now, I will say this though. I've only really watched a lot of the videos and read articles mostly about, you know, natively, compiled, M one arm apps and x86 applications, which they say.
The x86 applications on M one run better than on the Intel chips in most cases, which is fascinating, but I haven't really watched too many videos or gotten through all the videos where they were reviewing the, you know, iPad and iOS applications on. It, which I'm really fascinated about because that's a big selling feature.
And it seems as though Apple puts up a big sort of, Hey, these are available. I was looking at some of the screenshots, I think, in the store. It's like, this is an iPad application and trying to describe people why it may not be perfect because it's made for touch and there's no touch screen, which we've talked about.
So it's kind of a scary point because all of I'm assuming all of my iOS applications are now just available, but I can't, I don't know. Like I just don't know. And that's scary to me. 
Frank: [00:04:13] It is scary. Um, I keep, I'm curious if I just see like sales double won't that be cool? Um, it turns out 10 million people bought all these laptops all of a sudden and just started buying all the apps.
That'd be awesome, but I think no, the, uh, The volume is going to be low for a little while. Cause it's going to take time to roll out all this hardware. And so we're just not going to see it and sales for a while. And on top of that, like you said, we just don't have the hardware and we haven't been testing.
I think that's shame on us. I don't know. When were you able to first start testing your arm version of your app on the D D K. I've never been able to do that. 
James: [00:04:53] I've never been able to, I never made it off preview one. Unfortunately the first DTA I tried, I tried to upgrade it. I had problems. I've tried to force it through and it just didn't didn't work.
Um, but I, yeah, I've been waiting. I think that's the thing is I kinda kept waiting. I didn't believe that Apple was going to release these Mac books. And I guess also, I didn't believe that they would release them in such force to the point where really you can only buy a Mac book air with an M one processor.
And pretty much you can only buy a MacBook pro 13 with a M one processor. I know it's available, but why would you not buy it? I guess, especially with these glowing reviews, but you know, there's a big banner inside. That's been there for a long time, by the way, inside of the app store connect portal, which is iPhone and iPad apps on Apple, Silicon Macs.
You need to manage your availability today. And I also ignore that Frank, because I was like, Hey, I'm not going to happen. Not a big deal. Um, but it's still there. I'm looking at it and I don't know what to do. 
Frank: [00:05:52] Yeah. Yeah. I ignored it for a long time. Two more out of, I didn't know what to do. Um, because I have handwritten Mac versions of a lot of my apps.
Not, not all of them, but the ones I make money on I've written Mac versions of, and I was like, So do I, what happens? Like what happens when Apple actually releases this computer? When they go to the app store? If I have the check box saying yes, please put this into the Mac app store. Will they see. Two copies of my app, like a Mac version and then the iOS version, how will they be distinguished from each other?
Because as far as I know, they have identical titles, so that's a little bit weird. Um, and then just. Putting this down for the future. What's not top out just yet. Uh, Apple does have universal bundle IDs and I think in the future, that's the direction I'm going to go. But right now I have separate bundle IDs, separate apps, and I just, I got frozen.
I didn't know what to do. 
James: [00:06:59] Yeah. Like, is there a way in the developer portal to say, Hey, this app has been seen 5,000 times on iOS, but 10,000 times on Macko ass. Right. You know, I, I also don't know what that looks like. You know, I know that the review units are out there and people are probably starting to receive, um, things just in general.
Um, but yeah, I think. I I'm in a little bit easier of a situation because my applications are either only on Macko S or only on iOS. So to me, it's like a, no-brainer like, Hey, put them all in there. Right. Even though I've never tested any of them at all, 
Frank: [00:07:35] I think that's the problem. Like we haven't tested them at all.
So I've been doing catalyst work lately. So this is basically the same technology you're taking your iOS app and running it on. But not arm Intel x86, but as a Mac app. And as far as I can tell that it's all going through the same libraries as when you run your arm iOS app on the new Mac, it's still that same translation layer happening.
The big difference is fonts are scaled by 70% and that changes kind of the layout of your UI windows can be resized, those kinds of things. So I would say just from my experience, I would guess that your app is probably working pretty well, but it's so weird not knowing, right. Boy, I'm really starting to feel like a failure right now for not having tested all this 
James: [00:08:31] well.
And, and we also have to think about like, Are the in-app purchases working too. I think that's another question. I believe that you had to have recompiled your application against a newer version of X code, maybe for it to work. I'm not a hundred percent sure. I remember reading that somewhere and if I find it, I'll put it in the show, note links, but also how do I test in app purchases on my Mac?
Do I just assume that they work okay. Because what I don't want is. For people to leave reviews on the Mac version or the iOS Mac version. Like also, how does that work? Like if someone reviews my app on a Mac, is that going to show up on iOS too? Like, I don't actually know. 
Frank: [00:09:13] Uh, just guessing. Yes. Just because when you, when you log into app store connect and you look at the URLs, I happen to stare at the URLs a lot.
Uh, there's an iOS URL and a Mac you RL. And as far as I can tell, they still use that URL difference. So the big change that they have done to app store connect is when you create an. Application, they call it an application record in the documentation. You can now have Mac and iOS versions of your app listed there.
So that's kind of a cool feature in the past. When you create an app record, it had to be Mac or iOS, and now. With the unified bundle IDs, they all merged together. But again, it doesn't help me. That's great. Future tech. It doesn't help me making my decisions right now. So right now I've decided to be conservative.
I've decided that until I have. Me myself and I tested the software on one of these pieces of hardware. I don't want to start selling it. I have pride. I want quality software out there. Now that is for the apps that I have Mac versions of for the other apps that I only have iOS versions of just like you.
I'm like, yeah. What the heck thrown into this store? Go forward. Apple. Ah, 
James: [00:10:33] Frank, I just discovered the scariest thing in the entire world. Are you ready for this? Uh, 
Frank: [00:10:38] you haven't been recording though this time. 
James: [00:10:40] Oh, no, I've been recording. I went into the app store connect. I selected one of my iOS applications.
And then I went to the device tab and it says desktop 
Frank: [00:10:53] to, uh, to 
James: [00:10:55] do installs on desktop. That means people are writing an application on desktop. 
Frank: [00:11:01] It, which one was the, sorry, 
James: [00:11:03] this one is my scoreboard app. 
Frank: [00:11:05] Oh, cool. Okay. So two people have bought new Macs and needed some score-keeping. That is pretty cool, actually.
James: [00:11:15] I mean, that is the only way I can tell today if it's there. Cause it says iPhone iPad, desktop. Cause I was thinking of it. I was like, Oh okay. If I, if I look at all of my, you know, Different numbers on here. When I go to apps or connect, I look at device, I say, okay, well, desktop is my number one because my number one application is a Mac iOS application.
But if I tap on a specific app and I go, Oh, where does that go? You know? And where is it popping up? Is it on desktop or is it not? And it's totally there. So we at least have the capabilities there, but I think you are correct, which is. If someone then goes and reviews that application, then it's going to inherently be a review for that app.
Or is it a review of the app, which in now this app is running on multiple platforms. So we're review on any of the platforms is a review for all platforms. 
Frank: [00:12:12] Yes. Hashtag question Mark. It's how it feels right now. Uh, boy, uh, Apple really, uh, I think they kind of did this with 64 bit. Also remember back in the day, everyone's like we're doing 32 bit arm.
The Pearl is 32 bit. Life is good. And then Apple decided. Or just kind of out of the blue apples, like, Oh, by the way, iOS is 64 bit now and all your apps need to be 64 bit and we're going to require it on Mac. They did that transition pretty swiftly funny. Um, so I should've seen this coming, I guess. But again, I just delayed too long.
I am excited for you. You already got sales is after a free app or do you have to pay for it 
James: [00:12:58] one? Yeah, no, no paid apps yet. The animal crossing app is the, is the paid one. That's going to go free. If I ever decide to test my in-app purchases, logic that I need to finish at some sometime the Epic inclusion too.
I'm just way too lazy. I should just make it free and not even care about it, but I'm going to delay until Christmas. Maybe it'll be a Christmas miracle who knows. Um, okay. So, but let's get back here now that I've scared myself to death because I didn't check or uncheck any boxes. You did decide to collectively unchecked boxes.
Now on all of your applications are only on the ones that have. Mac applications. 
Frank: [00:13:38] Right? Right. So, so far all the ones that I've already written Mac versions of, I uncheck the box as, and my hope is they will be directed to download the x86 version, the x86 64 bit version, all my other iOS apps. I said, yes, go ahead and put onto the store except for one.
Did you get one of these emails? I got a nice email from Apple saying, hello, developer. Hello. We were testing your app for you. Look at us. How generous are we? And we ran it on our new awesome hardware and Oh boy, did it crash? 
James: [00:14:18] Oh, no. 
Frank: [00:14:20] Yeah. So they actually sent me a really nice email with a full crash rapport and a console log of everything going on, executing that app.
And I don't remember what the bug is. I don't think I can find that email that quickly, but it's kind of cool. So they're at least running their apps and, uh, making sure that at least. What don't crash before they put it up on the app store. So you didn't get one of those emails, all your apps 
James: [00:14:49] worked? No, apparently it, well, you know, it depends on where they sent the email.
This is a good question. I'm going to check literally all of my inboxes. 
Frank: [00:14:59] Okay. Colin, Apple. Yeah. Um, 
James: [00:15:02] let's see. 
Frank: [00:15:04] Uh, you'll be lucky. It's only one of my apps and I have, Ooh, I don't know. Eight apps up on the app store right now. So I 
James: [00:15:14] saw it looks okay. Yeah. 
Frank: [00:15:17] You're a better writer than I 
James: [00:15:18] am. You know, I don't see anything in there, but all my apps are simple applications, so they're nothing, nothing too crazy.
I would say in side of this. 
Frank: [00:15:28] Well, it's funny. The one that's crashing is my silly math game. That's just. And I messaged clone where you're just solving little math puzzles and that one is, it can't be more than a thousand lines of code. So I'm really curious how I managed to make that one crash. I think that's pretty impressive.
James: [00:15:48] So does that mean that a continuous works. 
Frank: [00:15:51] That's what I'm trying to figure out right now. I'm clicking around an app store connect. Where, where did you see the thing saying that you had a two downloads on desktop? 
James: [00:15:59] Okay. So when you, so this is, this would be a fun adventure for everyone. So when you go into your developer portal, you can click on apps or connect.
Now, the next thing that you're wanting to do is then launch app store connect, which is app store connect up apple.com. You want to go to sales and trends? Gosh, 
Frank: [00:16:14] that's where your trends. 
James: [00:16:16] Then you want to tap on units. Okay. So under sales there's units, then tap on continuous  
Frank: [00:16:25] circle, loading circle loading takes a while.
Sometimes it does 
James: [00:16:29] when you sell so many units like you Frank, 
Frank: [00:16:32] but the numbers add one at a time just to keep it all in suspense. 
James: [00:16:38] So now, instead of having a bunch of different bar charts, you have the one highlighted, then you can click on 
Frank: [00:16:43] device. Gotcha. Yeah. Uh, I, I will phone back when this is complete.
I will call back into the show. Okay, 
James: [00:16:51] nice. That's how you do it. So you kind of narrow it down. So 
Frank: [00:16:55] yeah, my, my plan is then, um, to either update this D DK or I don't think I'm going to get the air. I don't do I want a laptop. I was, I was planning on getting the mini version of it, uh, because that can just sit on my desk and whatever life is fine.
Yeah. But, uh, test it out myself. If I'm happy with how it's working or maybe I need to do an update to the app, get it into a state where I like it, and then I will enable it. Thank, but honestly I'm still debating for my current existing apps. 
James: [00:17:30] Yeah. I mean, I think for, it does make a lot of sense. If we think about what you have is in the past, you've developed two applications, one for iOS, one for Mac, very traditional, which makes sense.
This is a case where. Each of those applications, you've really fine tune for each operating system. And I think that the right call is what you made, which is, Hey, put my Mac app on the Mac, but my iOS app on the iOS and call it a good, because. You know, then you're in decision, which is like, Hey, do I use catalyst in the future?
Do I use this new fancy thing? Or do I keep, keep developing two applications? And for some of your, for some of your apps and may make complete sense to just keep them as is or else, you know, who knows what that is? I don't know what an upgrade cycle looks like. If you know, people move to the. No catalyst version or the magic non catalyst version.
Right. What does that look like? I think for the other applications, the state that I'm in and the state of the urine, which is like, Hey, I can now open up my application to millions of new users. It's kind of a no brainer besides the testing point of view. I think there's a point that scares us, which is, Hey, we're going to take people's money.
And we just hope magically that it works. And this. Is the conundrum, right? Which is, Hey, we often release applications and we haven't tested them. Every single piece of hardware. I haven't tested them on tons of, uh, iPad devices and I haven't tested them on and, you know, um, new, different iOS, iPhone versions.
And now we're saying, Hey, we also have to test that this thing will work on Mac iOS, then many people aren't going to have this hardware. So it's sort of. We're in the state, which is, let's say we didn't have the DTK days that we would have to go buy something to then test our application, which is what we've done forever.
Right. I mean, been theory that we've done that to a certain extent because it's like, well, if I run my, if I run my windows application on windows, I'm going to hope that it works on all versions of windows that I target where this case it's not only. Um, a new instruction set, but it's a completely different device at the same time.
So it's not only does my app work well, but there Iran, I should say. But does it actually work as a functional or is it so demanding of a touch screen that I want to turn it off? There's a lot of different, different things to work through in this decision process. 
Frank: [00:20:02] Yeah, actually, boy I'd even think about it in those terms.
That's really interesting. So, right. So it's not just a processor switch. It's also a userface ADM switch. You're going from screen to mouse and keyboard. And on top of that, it's an API switch because there are some new fancy API APIs to integrate better into macro S and that kind of stuff. So. Yeah, this, in some ways it is magical that your app just runs there, there definitely.
Now that you bring it up a lot of work to do, to make it run well there. And I'm curious about that for existing apps. 
James: [00:20:45] Yeah. Like you do, does your application have multitouch like, how does that work? 
Frank: [00:20:50] Multi window. So something we're running into is, uh, they introduced scenes and iOS 12 ish. Maybe I love it.
I don't remember. And unless you did file new project in the last year, you're probably not using scenes. I've. Been running apps for 10 years. I do not use scenes. And, but if you want multi windows support on Mac, you need to support UI scenes. So yeah, I've got to write that code, got to go interrogate my app delegates.
Cause you know, it's like the trash bin of iOS code. We all just throw our junk code in there. So now I've got to figure that out. 
James: [00:21:29] Yeah. You know, there's, there's so many things that we've talked about, catalysts a lot in the past, we talked about our excitement for this, but I don't think we ever really sat down to think about all of the implications that this has on us.
So it's almost, it's almost to some weird extent to be overly cautious, too. Actually uncheck all of your applications first and say, no, no, no, let me hold off. Like, who's going to be mad. You know that it's not there. It's not, it's not on Mac yet. It's only available to these new people. So in my mind, I'm almost thinking, should I just remove and uncheck everything to 
Frank: [00:22:05] begin with?
It's a toughie. Um, I would say it's just, uh, how quickly do you think you can get to it? You know, maybe if you can get, uh, get a DK. I remember you probably can't get a DTK anymore. Uh, so if you can buy a new computer now, uh, yeah. Um, maybe leave it up in the hopes that it does work. I'm an optimist. It's going to work.
Apple does a good job, but, uh, just be prepared to take it down really fast. If you realize that it's a terrible on there. And well, you can always pay attention to your reviews, but reviews are legged by like two or three days kind of minimum. So it's kind of hard to tell from reviews also. And who's going to notice what those two people, those two people that bought your app, they're going to notice.
I think in the future though, um, This is still the direction I want to go. Even with all these transitional problems and all that. I'm still excited for basing my apps around kind of UI kit and focusing in on that. So they must have the in-app purchase story figured out. It's just going to be fun, signing things, right.
It's just get the right certificate and the right profiles and all of that. I'm sure all of that's just going to be such a bear, but. It's kind of the future direction ever thing. So don't fight the wave. 
James: [00:23:27] Yeah, I really feel as though right now, if I'm looking at my apps in the app store that. I really need to be thinking about taking my applications too catalyst.
I know we're not there yet. On the Xamarin side of things, I know you're working through some things. The teams are working through some things, but I feel as though now it's all real in my mind. It's all real in my mind. Apple made it real. Dang you that's. Yeah, I didn't have to think about, I didn't have to think about catalyst forever.
I would say are the things I wanted, like, these are nice to haves, but now if my applications are on M one chips, It really means that I can't stick a button on my website that says, get it on Macko ass. And then only 1% of the Mack population can get it. That's kind of stinky. You know, I kind of feel as though for me to really have this story, I need to go further and hope and work on that catalyst support so we can say, Hey, my application is.
Over on this and that's, again, another, that's a different test case, right? Because if you do a catalyst application and there's a good question for you, Frank, if you do a catalyst application, what is running on the M one chip? Is it your catalyst app or is it your iOS application? Non catalyst? Like once you go catalyst, is everything catalyst on a mag, no matter what.
Frank: [00:24:47] No, they do have universal binaries yet. Again, some other crazy form of universal packaging. So you can ship. X86 and, um, arm versions of your code, but wait, I'm sorry. I guess I just contradicted myself. So I guess that is capitalist because that's essentially the same app, just compiled for the two different processors and you can ship that way.
I haven't looked into it in particular because the way the app store connect is set up, you can still just do two builds. So upload an iOS version, upload a Mac version and. They can either share a bundle ID. And that means if they buy it on one, they get it on the other, or you can have two different bundle IDs.
And that means they have to buy them in those individuals stores. Or if you check the box, then the real confusion happens and the iOS one can be on the Mac store 
James: [00:25:44] also. Ah, I see. So here's what really needs, Oh no, this is very fascinating. Yeah. So if this is a weird, so if your, if your application. Is, Oh, this is strange.
If your application is out today on M one and then you release a catalyst aversion later, that technically would be a Mac application and would be a different skew. 
Frank: [00:26:14] Well, it's, it's up to you, you now, because nowadays one app record as they call it, or you can think of it as a bundle ID, but it's not quite the same.
So one app record and app store connect can have multiple platforms associated with it. And I guess the way I think about, and that's the SKU. Yeah. So your app record is a SKU. 
James: [00:26:35] Got it. So that would be, that would be good. And then if they had a version of the  app, That's just working and you release a new version of the macro S catalyst app.
The app would upgrade and technically it should look and feel the same because in that case, a catalyst app is an iOS application. So really it's the same application running. It just depends if it's going to work on more operating systems. So you really do want to have that shared bundle app ID for this to work 
Frank: [00:27:03] properly.
Yeah. Um, I was fighting it a tiny bit because I feel like I've profit a little bit from habit. Having people purchase separately on iOS versus Mac. And I justify it by saying, I, I spend time, uh, keeping these two versions in, in sync with each other and feature rich on the Mac feature rich on iOS. But I think.
I can't really justify that anymore. And I'm going to simplify my life by having. A, a unified bundle ID, but B by using that and using catalyst and UI kit, so that I'm just writing against one API, it's just a simplification. Um, it's simpler. It's more simple from the user's perspective and it sure is a lot less maintenance work from my perspective.
James: [00:27:59] Yeah. This, this, this to me. Is the longterm, especially as an independent developer, you're a developer of one, you know, how do you reduce your support tickets? How do you reduce your monitoring? How do you support your, you know, reduce your maintenance longterm, and how will it enable you to work on other applications while it's going to enable you to work on more applications?
When you have to support one less application? Technically, you know, and you're going to replace one of them going forward with the other one. It would be very fascinating to see how a Calca or a I circuit would work if since both of them are already like, is there any way to unify them today? You know what I mean?
Frank: [00:28:52] Right. So I, that section in the Apple documentation and they say there is no way to unify to existing app records. Their recommendation is to retire one and then put the other platform into the other existing one. So. Probably what I would do is retire the Mac app record and then start uploading Mac binaries into the iOS, the formerly iOS app record.
That was their suggestion. 
James: [00:29:21] It's almost one. Whichever one has the most downloads. Yeah. 
Frank: [00:29:25] In a weird way. 
James: [00:29:28] Yeah. Especially if it's a paid application, you almost want, it's a weird way of saying it, but like, Hey, if a million people downloaded on iOS and a thousand people on Mac. You want to give a million people the free version of the Mac instead of a thousand people, the free version of the iOS version in a way, 
Frank: [00:29:46] uh, it's it's it's complicated.
Can I throw you a curve ball? 
James: [00:29:49] Sure. 
Frank: [00:29:50] So I've been working on I circuit 3d and throughout this whole time I've been maintaining an iOS and Mac version who. Yeah. So do I, I do I release them in that form or do I wait a month and get my catalyst work into good shape and, uh, do that. It's a real debate I'm having, because there's definitely pros and cons on both sides.
The con is I have to delay and I'm, uh, riding on some experimental technology. The pro is that radical simplification. Long-term, you know, um, Doing something painful in the short term for long-term benefits. So it's a tough debate I'm having. 
James: [00:30:34] Yeah, the, obviously the thing that you could do is release only on iOS and then consider your implications on Macko S right.
No matter what it feels as though you're going to have to have a universal skew here. So if you release on iOS, you will technically have released on Mac, but only for. Um, one processors, you know, um, you haven't released that native Mac application, so you could have, it's so tricky. I feel you have to make the decision to not upload the Mac version.
So you can decide later what to do with the Mac version or, or you could release the Mac version and then it has to be. The same feature parody as the iOS version, right? That's your conundrum like is the iOS version at the same feature level of Mac S and if they're not, then that's a real problem. 
Frank: [00:31:29] Well, it's a little worse than that because the Mac version is better because Macs are more powerful than iOS.
So I have a lot of features tuned down, you know, settings tuned down to run on iOS. Whereas the Mac version, I can just crank everything. Oh. And the app runs gloriously and that kind of stuff, but that's things where I can do. Settings and more adaptive instead of, you know, hard coding them. They're not even hard-coded right now, but it's just more like defaults and things like that are different between them.
But we think I, like I decided exactly. All right. So far I've decided exactly what you said. Uh, start with a universal bundle ID on iOS. Get that thing, shipping, get it running. Somehow get myself a new version of, um, Macko S and see how good it is on the Mac. See how hard it is to get a good on a Mac, give myself, say a month to make that decision.
And then I'll be able to decide if I want to ship the Mac version or continue on with the UI kit version. Nice. 
James: [00:32:37] Yeah. And I think it's, it's, I think there's a few people probably in the state and I'm interested to see what are our listeners. If you're in the same position too, or maybe you've already bought a new MacBook air and you're testing out all these iOS, it feel weird that we're, that we haven't done it yet.
I feel like we're behind. So we're only guessing at everything. I mean, we should be the experts on this RSR, everybody that you maybe came into this episode and you're like, here's a review of how everything is working, but ne we are just giving you our insight into. The app developer conundrum that we're in at this space.
But if you have one of these new Mac books, definitely would be fascinated to, to, to write in either on Twitter or via email on merchant conflict out of him and let us know how things are going and or what are you doing with your applications? Because I don't know if everyone's, it's so easy to, to, to just not do anything, you know, if you just don't do anything and then things happen, but.
You should probably maybe think about some things. 
Frank: [00:33:38] Yeah. And if you're selling on the store, what is the cheapest model? I think you're going to have to spend seven or $800. So you're just going to have to make that decision of do I want to fly blind and just hope for the best or scrounge up $800 somehow borrow it from a friend and go buy herself a new Mac and see how well your apps run on it.
James: [00:34:02] I think this weekend, I'm going to be sitting by my DTK and hoping and praying that a power is on and I can put it in recovery mode and try to upgrade it again. So we'll see, because 
Frank: [00:34:13] if not, we can, we can live stream mine though. I have no idea how and how long an installation is going to take. So I'm not sure if that would actually be fun, live streamed.
James: [00:34:23] Well, maybe you can get it up and running. First, maybe we'll see when he can point a camera at it and watch it. I will say I did up update my Mac S um, or my MacBook pro 2013, which apparently is having tons of issues from the internet. I think mine updated. I didn't turn it on, but, um, I'm going to my weight.
I was on the one of the previews. I'm not on the final builds. I may wait a little bit because people were saying there was issues with it, but even that, that took hours to update. So it's a pretty BV up. So prepare yourself. 
Frank: [00:34:53] So just from me playing around with it, I find that like all you're kind of a first party software.
So all the Apple software works. Absolutely. Just fine on it. A lot of your big brand software, big co software that runs just fine on it. The. Bad parts seem to all be around like audio and video and things like that. Ironically games seem to work fine on it. So it's just those like professional tools that might be a little weird.
I've personally hesitated putting it on my deaf machine, but I think I have to, yeah. Put on my big boy pants and go for it. 
James: [00:35:30] I think I'm in the same boat as you. I mean, I, I, I needed, I need to run something. I need to test it out. I usually wait like almost a year to, to install the latest version of Mac iOS, but I'm going to make it happen then I'm ready.
I'm scared. There's gonna be the last update that this machine definitely gets. Cause it's, it's the last, it's the oldest Mac book pro that can install big, sir. It's the very last one. 
Frank: [00:35:55] Oh, is that right? Okay. So not the adorable, I wasn't sure if you were talking about the adorable, 
James: [00:36:00] uh, the adorable could probably run it, but that is in quarantine, in Redmond.
So I do not have access to that machine. 
Frank: [00:36:07] Boy, I forgotten someday. They'll let it out. 
James: [00:36:10] The number one. Yeah, it's a bunch of, um, monkeys or, uh, you know, my, my Xamarin monkeys are locked up inside of that with my, my surface book, two 15 inch and my MacBook horrible. They're locked up in quarantine. So not that I need them, but they're there.
Don't 
Frank: [00:36:25] you get like a task rabbit and a hazmat suit. I don't, 
James: [00:36:29] they can't get in. It's a lens and lockdown on again, badge. So I don't know. 
Frank: [00:36:35] So what did we, what did we learn today? What lesson did we learn today? Uh, we're behind, but don't worry. It's rough times we book catch up Apple. None of us expected Apple to follow through on this.
Ha ha jokes on us. So w we'll do a better job at catching 
James: [00:36:50] up? Yes. And go into the app store connect, check out your sales. Do you have an update at all? Did it update, did anyone download your app on desktop? 
Frank: [00:36:56] As far as I can tell, I only checked continuous, but no, one's bought it a sad Panda. Okay. Maybe the free apps everyone's going for the free apps.
James: [00:37:05] Yeah. There you go. All right. Well, I think it's going to do it for this week's merge conflicts. Please write in and let us know what situation you're in. Is it going better than our situation? Do you have one of these devices? Let us know, go to merge conflict.fm and click on that contact button. Hop in discord or send us a tweet.
That's gonna do it for this week's podcast. And until next time, I'm James Monson magnet 
Frank: [00:37:25] and I'm Frank Krueger. Thanks for listening.