2,320 karma · joined May 12, 2014
As someone who makes apps in the health space, I couldn’t care less if other tracker data was integrated into HealthKit. HealthKit honestly sucks - it's some bastard of objc naming schemes and methods jammed into Swift. The async is horrible to debug, too. No one has a good time in HK.
The issue with other trackers is that they are more locked down than Apple. You can't just get HR from Oura for instance - and that's not a health kit issue either.
This type of mindset will be the end of Apple.
Personally I see avenues for both outcomes.
https://s3.documentcloud.org/documents/24492020/doj-apple-an...
Either that, or Apple's management has become truly rotten. That would be the saddest realization.
Am I understanding the docs correctly that you don't have a local library available (the SDKs are just calling the APIs right?)? Mind going through why you chose a remote API?
--------
tell application "Messages" set phoneNumber to "+15555555555" set messageToSend to "This is a test!"
try set iMessageService to (1st account whose service type = iMessage) set iMessageBuddy to participant phoneNumber of iMessageService
if exists iMessageBuddy then
set theMessage to send messageToSend to iMessageBuddy
delay 2 -- Wait for a short time to allow the message status to update
if status of theMessage is not "delivered" then
error "iMessage not delivered"
else
log ("sent as iMessage to: " & phoneNumber)
end if
else
error "Not an iMessage user"
end if
on error
try
set SMSService to (1st account whose service type = SMS)
set SMSBuddy to participant phoneNumber of SMSService
send messageToSend to SMSBuddy
log ("sent as SMS to: " & phoneNumber)
on error
log ("ERROR: COULD NOT SEND TO: " & phoneNumber)
end try
end try
end tell(lose your main iCloud account... 'bold move Cotton')
Still don’t know how they get around auto send, iMessage required user input last time I tried this
[Edit] Shortcuts still require user interaction, apparently mac does not, that's interesting
Did you ever have to store custom metadata in NSAS to file? Before chatGPT, I had to write NSSecureCoding classes by hand, and that agony will remain in my soul next incarnation.
For reference, Let's build the GPT Tokenizer https://www.youtube.com/watch?v=zduSFxRajkE
Turning on a light bulb, ordinary light in the house, meh, ok, then swipe your hands out over the counter and the recipe pulls up. That's the 'oh wow' moment. Then grab and throw a song to a Homepod connection. You know what I mean...
There's a gap someone can shoot, maybe 3 years tops. Honestly though, the developer ecosystem is just so tight, continuity so powerful, doing this solo requires more than what the whole MFi program offers.
Whatever, it at least gives a startup an opportunity to build something unique - it's just sad to see your old friend start going senile.
> We were allowed to expense all employee compensation tied to software or R&D in the year in which we paid it. Now we can only expense a small fraction of that because we have to capitalize the expense. That means if you paid and developer $100 to develop a piece of software then sold subscriptions totaling $100 you now have a profit. The old model you have zero dollars in profit the new model says you have something like $80 in profit that you know have to pay taxes on… with what cash?
Additional "finger in the wind context": this change was brought about through the Trump Tax Cuts. My best guess is that Trump wanted the 174 change as a negotiation token to prod tech to make a deal. Mind you and me, this was all pre-pandemic. The financial world was pretty stable and this was going to be a 'great way' to make people work together, if desired. After the pandemic financial response, all bets were off.
Soloprenuers are the only one's somewhat immune. I'm thankful my companies needed to downsize before this.
Final context, there will be a whole new industry to define the useful life for a piece of software given the advancements in AI. This is going to be great fun.
[edit] One more thing, this change was thought to be “repeal-able” with new legislation. Since it no longer looks to be the case, to avoid “everything is securities fraud” (Matt Levine term), everyone has to adjust their public statements and accounting for this new change. Sure many of the big players will still make profit, but analysts only care about “beats and misses.” And since the legislation hasn’t passed to put the old rules back in place, accounting has to make these forecasts more permanent with less wiggle room - aka misses and forecasts down. Now, there is a huge op to trade the rules changing back - which would be a huge tailwind (made headcount cuts and get favorable tax treatment)
The rules of the game have changed. We were allowed to expense all employee compensation tied to software or R&D in the year in which we paid it. Now we can only expense a small fraction of that because we have to capitalize the expense. That means if you paid and developer $100 to develop a piece of software then sold subscriptions totaling $100 you now have a profit. The old model you have zero dollars in profit the new model says you have something like $80 in profit that you know have to pay taxes on… with what cash?
Yeah my working theory is that Trump thought he would still be in office to use this as a negotiation token to bring big tech to the table.
For example, if you were to hire a group of writers, ghost writers to be specific, to re-create someone else’s work, then publish it yourself as your own who is at fault? Who gets sued? Is it you who directed the writers to do the work or is it the writers who did the work?
So if we accept this model, the owner/onus is on the prompter to not re-create copyrighted works.
(Albeit an assumption that the writers are unaware to some extent)