"Error handling" part is absolutely brilliant! Thanks a lot!
@ek-bhartiya-nagrik4 ай бұрын
Paul is a great instructor and an amazing resource for the iOS community. He is very credible, person too.
@Alperic274 ай бұрын
oh the fun of narcissism …. 🤦♂️🤦♂️🤦♂️
@0xjorgev5 ай бұрын
Another great talk by Paul!
@asadchattha34705 ай бұрын
Best🥇instructor ❤
@Prashant-75 ай бұрын
When you use closure in environment that's I have seen first time , is it safe to use ? does it cause retain cycle ?
@trendz44225 ай бұрын
My favourite teacher.
@RobertHolzapfel5 ай бұрын
Wow, thanks. Your talk gives important insights into that common challenge, it is wise, though funny to listen, a rare combination. 👍🏻
@shercalderaro373811 ай бұрын
Promo_SM 👌
@AbinBaby28 Жыл бұрын
Great talk. I just started learning rxSwift and the takeaway from this talk is very helpful.
@incelemeTRe Жыл бұрын
This lecture was awesome. Very fun and clear.
@honeybadger9162 жыл бұрын
wow this is a good rxswift intro so far. it made the concepts clear to me
@casperes09122 жыл бұрын
Someone help me understand the German joke
@zeleuny2 жыл бұрын
What lies between “vier” (4) and “sechs” (6)? Fünf (5)…
@smilebot4843 жыл бұрын
A computed property would reflect canMakePurchase! So that's a bit dumb.
@shaimishali14162 жыл бұрын
No, since there's no way to observe change on a computed property. You'll have to constantly poll it.
@Srinadh583 жыл бұрын
Nikolas, Thanks for the clear picture of GraphQL for beginners. I have one question. Can we use the same fragments on multiple queries? For example, list of conferences and filter on the list of the conference? So one place fragment will have only few fields and another place fragment will have a few more extra fileds.
@calebrowley44193 жыл бұрын
Very well done! The way he started with previous data passing methods and then went to combine was very helpful. His explanation of combine was clear and made the most sense for me out of the videos I've watched so far. Thank you so much for the presentation and video.
@lukaszstocki69983 жыл бұрын
Cool presentation! The thing to note in t13:49 is that a.textContainer and b.textContainer are pointing to the same instance of TextContainer. Line "var b = a" does create a copy but what is copied is a reference to the same object :) If someone is interested more in this then existential and value witness conttainers are the keywords to search for :)
@ssaai4 жыл бұрын
@paul 👏🏻👏🏻👏🏻👏🏻👏🏻 👍🏻
@tiojoe_4 жыл бұрын
Is it possible to have source code? Excellent Talk!
@yixe22534 жыл бұрын
YAY swiftcon is back!
@gfrias064 жыл бұрын
Awesome tutorial, thanks!
@khanhtoanle83964 жыл бұрын
How can u code Swift in a Ipad?
@yixe22534 жыл бұрын
Please upload this years talks
@sunilaruru92574 жыл бұрын
This the best video on Rxswift so far.Thanks a lot @shaiMishali
@jafarkhan3495 жыл бұрын
Awesome!! Really informative
@iosplus67025 жыл бұрын
how to use graphql with offline storage on IOS ? I need to save the data on the cash on offline storage in case the client open the app offline. any complete example?
@ninja4ever_5 жыл бұрын
1:10 agenda 1:55 what is Rx 8:00 building block 28:40 RxCocoa 37:15 debunking some myth 41:00 3rd party lib 43:40 resources 45:40 QA
@blazefrostrider5 жыл бұрын
Great Talk buddy !
@MangoDeveloper5 жыл бұрын
Really nice. Thanks for sharing all that knowledge with us.
@leontea70705 жыл бұрын
The best RxSwift tutorial for beginners! The first RxSwift tutorial you should watch!
@leontea70705 жыл бұрын
I started coding using RxSwift a few days ago and I have my brain bended already!
@ShaiMishali5 жыл бұрын
You'll get there! One step at a time :)
@nathan430825 жыл бұрын
The problem with your headset mic is that the noise gate was set too aggressively.
@ShaiMishali5 жыл бұрын
It was actually just a bad headset :) Otherwise the other mic would be affected by the same processing. Anyways, it was unfortunate but not a huge deal. Hope you've enjoyed the talk, regardless! 😇
@nathan430825 жыл бұрын
@@ShaiMishali Yep. Good stuff. Thanks!
@mnesvat5 жыл бұрын
Good talk 👍
@rudy121185 жыл бұрын
Excellent talk. There's so much to learn from this video!
@hoochill5 жыл бұрын
How is api.swift generated?
@ChrisComeau5 жыл бұрын
It's in the custom build phase, see 23:00
@ilovepickles74275 жыл бұрын
I like the way Daniel weaves personal stories into the talk. Very compelling. Great talk. Wise man.
@Muescha5 жыл бұрын
Just a note: if your are in Germany and you create an action, then you get an error "you need to create a "Bereich" in Organisation. but there is an organisation under manage orgs. Solution: close the error message and on the navigation there is dropdown and change the selection from "Germany" to "United Kingdom" (see the country dropdown at 10:21) . after this select your org and section and you can create actions
@rudy121185 жыл бұрын
Excellent talk. Loved it! Paul is awesome. Incredible funny and his talks are always simple and concise
@issacroberto85352 жыл бұрын
Instablaster.
@kaunteyasuryawanshi5 жыл бұрын
That was a quite informative talk. Thanks
@vkasci5 жыл бұрын
A lot of fancy memes but nothing extraordinary, just obvious processes and ideas for any large software product company.
@chiliec5 жыл бұрын
Egor, your cats are beautiful!
@michilandrosov94685 жыл бұрын
Егор будто текст наизусть выучил:) Крутяк!
@w0mblemania5 жыл бұрын
"If you want to do UIViewController animated transitions, then don't." OK, so what is an alternative to the UIViewController transition API?
@djkim246016 жыл бұрын
Great talk! Thanks a bunch.
@quentinturner37536 жыл бұрын
Also can you have a navigation bar on top of you’re ar camera view
@quentinturner37536 жыл бұрын
Very good talk. Thanks a lot! But I’m just having a hard time grasping the difference between interact with arkit and interact with SceneKit. Could someone help me out please
@rompelstilchen396 жыл бұрын
Hi Quentin, it can be hard to get your head around in first place. ARKit interaction are based on ARKit scene recognition (in the real world) (ie.: ARAnchor et ARPlaneAnchor) and are used to position content in your scene, after plane is detected (like a ray hit test with real world content): `sceneView.hitTest(location, types: .existingPlane)` SceneKit interaction are based on your scene kit content (in your virtual world) (ie: SCNNode) and are used to interact (touch, pinch, ...) with existing content in your virtual SceneKit scene, after you've place some content in it (a ray hit test with virtual world content): `sceneView.hitTest(location, options: nil)` It's confusing because both methods are named `hitTest` and take a 2d location on your screen but they refer to each framework methods (ARKit and SceneKit). Hope this helps
@quentinturner37536 жыл бұрын
Thank you so much this helped me out a lot! I have one more question about your talk. You quickly went over how you could allow something to happen only after you have detected the initial plane. This is literally the only problem I have left in my projects code so I’d love some feedback on ways to have the correct amount of plane detection be the absolute first thing you have to inside the app before you can go on to adding geometry or changing UI anything really! Thanks again
@quentinturner37536 жыл бұрын
Hugues BERNET-ROLLANDE just to clarify, around 33:36 you said set up a delegate to let the hit test start working after a plane is detected! This is specifically what I am asking how to do or if there is any example code/projects out there that could point me in the right direction to do that! Sorry for my wacky questioning from the last comment lol thanks again
@rompelstilchen396 жыл бұрын
Quentin Turner not sure I understand your question. Once you’ve detected a plane, depending of your app usage you can and should turn off plane detection. As explained in Apple documentation: Allow time for plane detection to produce clear results, and disable plane detection when you have the results you need. Hope this helps.
@quentinturner37536 жыл бұрын
Hugues BERNET-ROLLANDE Hugues BERNET-ROLLANDE You said allow enough “time” for the scanning process before doing something like adding UI element to the screen or placing geometry on a plane. However I’d like to know how to only allow those things to happen based on a specific amount of surface area scanned (say about a 5-10 foot plane) instead of just time scanned before you add a geometry or UI element. If that makes sense lol I’m trying so hard to explain correctly so thank you so much for you’re patients I truly thank you