Earlier quoted context omitted.
> But if you are successful, there is a chance of getting sherlocked, so its a risky business model. What does this even mean? Watson shows up to help out?
Watson was an independent search application on Mac OS, until Apple basically photocopied it and named theirs Sherlock. Since then it's become a verb for when Apple takes your app and builds it into the OS. Another blatant example was Dashboard, which copied Konfabulator, Night Shift is a copy of F.lux, etc.
Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
41–50 of 75 posts
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#42Earlier quoted context omitted.
Watson was an independent search application on Mac OS, until Apple basically photocopied it and named theirs Sherlock. Since then it's become a verb for when Apple takes your app and builds it into the OS. Another blatant example was Dashboard, which copied Konfabulator, Night Shift is a copy of F.lux, etc.
Technically Sherlock predates Watson, it's just a lot of the useful additional features added by Watson were copied to Sherlock.
So the Watson name was probably inspired by Apple's from previous versions, but the Sherlock 3 feature set definitely got cloned from Karelia's.
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#43People with limited storage on low-end device don't have enough memory to store the apps.
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#44I remember when pose detection was announced, showing an app that corrected your workout movements. i have yet to see an app that actually does that. i'd love to have the equivalent of a personal trainer showing me where i need to adjust my pose in say pushups or other simple excercies. thus im equally sceptical of seeing these apis used. it seems developers are mostly porting web apps to all platforms ignoring neat…
There are multiple apps in the App Store that do this. I spent last year implementing pose detection in an exercise app and we used both Apple’s pose detection and a 3rd party’s. The pose (each point of the human form) itself was sent to a machine learning backend at around 30 fps, analyzed, and data returned at about the same speed using gRPC. Each exercise had a set of specific feedback for both positioning (“Stand…
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#45I remember when pose detection was announced, showing an app that corrected your workout movements. i have yet to see an app that actually does that. i'd love to have the equivalent of a personal trainer showing me where i need to adjust my pose in say pushups or other simple excercies. thus im equally sceptical of seeing these apis used. it seems developers are mostly porting web apps to all platforms ignoring neat…
The “there’s an app for that” world where small to medium sized teams can build a very iOS native app that takes advantage of the latest and greatest of the device is long gone. It’s kinda weird how Apple doesn’t realize this and continues to build for that world. Maybe if they were willing to shift on their % for devs that do build that way but unless they did there just isn’t the audience buying apps outright and t…
The standard reason given is that iPhone users are much more valuable than Android users, in that they're a lot more likely to pay for things. If I'm creating a workout app with a fancy form-correction feature then I might well want to use Apple-platform things that make it quicker to develop, at the cost to me of only slightly restricting my actual market.
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#46Earlier quoted context omitted.
Can download an Xcode project and view documentation here: https://developer.apple.com/documentation/vision/detecting_a...
Thanks. Where can we find bindings for other non-Swift languages? Or does the 'embedding for 27 lang' in the title refer to 'human language recognition' and not 'programming language binding'?
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#47I remember when pose detection was announced, showing an app that corrected your workout movements. i have yet to see an app that actually does that. i'd love to have the equivalent of a personal trainer showing me where i need to adjust my pose in say pushups or other simple excercies. thus im equally sceptical of seeing these apis used. it seems developers are mostly porting web apps to all platforms ignoring neat…
- Demo: https://www.formguru.fitness/video/c96fa975-fd9e-4912-8f60-1...
- Blog: https://blog.getguru.ai/guru-sports-powering-the-top-prospec...
- Customers: https://www.cadoo.io/, https://www.breakawaydata.com/, https://pharosfit.com/, https://www.producthunt.com/posts/fitx.
We've trained our own models (and customers can finetune them), but it exports cleanly to iOS (and Android!).
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#48Earlier quoted context omitted.
Thanks. Where can we find bindings for other non-Swift languages? Or does the 'embedding for 27 lang' in the title refer to 'human language recognition' and not 'programming language binding'?
Given that the talk about 27 languages is about natural language processing, you can probably figure out the answer.
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#49I would be interested to know of a consistent, on-board embeddings model. Trying to reduce latency and dependence on API calls for simple vector database search will go a long wag
https://developer.apple.com/documentation/naturallanguage/nl...
Re: Apple releasing segmentation/pose for humans and animals, embedding for 27 lang
#50Earlier quoted context omitted.
The signal to noise in fitness apps is high. The mainstream ones don’t do this, or if they do the implementation is so bad it’s not worth using, and discovery of anything else is fraught with shitware that wants a subscription to “unlock” it’s unknown potential.
Did you mean to say signal-to-noise [ratio] is _low_? Meaning that you get way too much noise for the amount of signal. Or did you mean to say it needs to be high (I.e. low noise) to be useful?
The amount of noise in Fitness apps is so high, nobody really dares to try out small apps. Therefore cool implementations from small devs like the workout-correction might stay unnoticed for years.