corneliusmark.bsky.social
Innovative tech developer making a mark in the app development world. Need innovation/developer for your app? Contact me. ⬇️
1,060 posts
83 followers
16 following
Regular Contributor
Active Commenter
comment in response to
post
I'm using an 16" MacBook Pro with an M1 Pro.
comment in response to
post
EventKit got an upgrade to a Foundation interface back in 2014 or so. Before that it was a Core Foundation interface.
comment in response to
post
I haven't touched this at all, but I would look at the NSUserActivity API on the ViewController or its SwiftUI counterpart. As that's how it works on iOS.
comment in response to
post
It brings in more money than the ad revenue.
I've found that, a donation page, to donate money in the app delivers more money, when positioned correctly makes more money than ads or Remove Ads In App Purchases.
comment in response to
post
LOL. Apple copied Xerox back in the day with the graphical interface of the first Macintosh.
comment in response to
post
Objective-C is an extension of C. Just like C++ is. The difficult part for most new engineers is its syntax as it requires you to count brackets to understand the meaning of a statement until your brain start doing it automatically.
comment in response to
post
Don't use the air for use with Xcode. Go at least for a Pro and yes my M1 Pro is up for replacement too.
comment in response to
post
This is actually fairly easy to do in AppKit. As AutoLayout does a lot of the magic.
comment in response to
post
Absolutely.
Be like Samsung. Apple makes the iPhone. Samsung copies it and calls it the Galaxy. Samsung becomes a cheaper alternative, starts making their own decision for subsequent models and becomes the 2nd largest phone company.
comment in response to
post
Even with Core Audio you don't have access to other processes audio. I suspect this can be done at the kernel level.
comment in response to
post
Yes, don't sell the features. Sell the or dream the user has.
comment in response to
post
I remember doing this with NSStream and its subclasses back in the day.
Yes, I agree. It's an improvement when it comes to amount of work to open a connection. As the NSStream version took about 100 lines of code to be able to do.
comment in response to
post
I do this because the entire tool chain and libraries are fully developed and when you're using SwiftUI, it's not. It's still under development. And developing with UIKit is still a lot faster than SwiftUI.
comment in response to
post
For example:
I still develop with a basis of UIKit for apps that support below iOS 17 and that's currently still all of the ones I have under maintenance.
comment in response to
post
Always trail a bit behind on technology with Xcode. As the front line of the available features is full of issues.
comment in response to
post
Dependencies man.
It's all needed.
comment in response to
post
I don't think it is in the cards at all. Multithreaded access comes with a performance penalty. And you can still access from multiple threads through different NSManagedObjectContexts on different threads and requesting the respective Object based on ID.
comment in response to
post
From there start asking questions on how to optimize your design process for speed. So you can produce more in a shorter time frame.
comment in response to
post
Then start approaching other designers and engineers to have a look at your designs. Get some feedback from them.
comment in response to
post
Once you get the hang of being able to copy UI's. Create a full design for an app. Repeat that a couple of times.
comment in response to
post
I know this is tedious, but I'd start by learning the skill on how to use Figma or Sketch by building existing designs from dribbble or other websites to show cases designs.
comment in response to
post
Luckily this will be taken care of by the frameworks when imagery and other assets are added to the project using .xcassets.
comment in response to
post
That's a bad thing.
Singletons have a good use case, where they're advantageous.
comment in response to
post
Oh, this might be some very interesting math to go over some time.
comment in response to
post
I don't know. I'm currently going through the wwdc23 videos. As I'm always trailing 3 years behind. As that's how far back I support for apps.
comment in response to
post
Interesting.
I expect Apple to solve this by delivering an extra binary in the App Bundle. Like they've done with async await support on the release of iOS 15 or the delivery of the Swift frameworks for version prior to iOS 12.4
comment in response to
post
Unskilled UIKit engineers make Massive ViewControllers.
Unskilled SwiftUI engineers make very difficult to understand navigation patterns.
comment in response to
post
Windows is not a Unix-based system and is not POSIX-certified. However, Microsoft has introduced mechanisms to support POSIX-like functionality, primarily for compatibility with Unix applications.
comment in response to
post
MacOS is a Unix-based system, POSIX certified with the POSIX.1-2001 standard and has full support for the POSIX APIs (e.g., fork(), exec(), pthread, file system operations like open(), read(), write()).
comment in response to
post
Too bad most those sessions are during night time in my time zone.
comment in response to
post
Most engineers prefer a Unix/Linux command prompt. MacOS is Unix. So it already has that. Windows on the other hand has the Unix/Linux prompt added to it. But it's still not Unix or Linux.
comment in response to
post
At least UIApplicationDelegate and NSApplicationDelegate aren't obsolete.
comment in response to
post
Fun fact: Hello World was a lot more work back then.
comment in response to
post
Sure just followed you.
comment in response to
post
This is a huge deal. And the plugging in other LLM's is probably due to EU compliance.
comment in response to
post
Yes, it feels like this was just put together without the attention for detail that Steve Jobs enforced around himself.
comment in response to
post
This.
Design first. Build later. As soon as you start building changes become more expensive to do.
comment in response to
post
It has been explicitly said it was for Apple Silicon.
Also at the end of State of the Union was said that MacOS Tahoe is the last one for Intel Macs. So they're phasing those out.
comment in response to
post
I actually love connecting.
Feel free to send me a DM anytime.