It was on one of the early versions of the Yelp iOS app as well. Don't really remember if it was there on day one, but I remember playing around with it in iOS 2 or 3.
Exactly. It’s an abstraction, you will always be a few libraries and components away from implementing what you actually want, but that’s a lot to build on just to use a system provided tool. For instance, I’m working on upgrading my company’s app to use iOS 11’s new password auto fill APIs. All it needs is for you to set the UITextField’s contentType properly to one of a dozen enumerated values, in this case Username and Password. React Native doesn’t expose that propertie on the TextField component however, so I have to either build my own extension on top of the TextField component or form the React Native project and submit a PR to get this feature working, a feature that’s explicitly supposed to be painless to implement. There are so many cases like this around React Native, the community mindset is usually just to find another dependency to integrate.
“the community mindset is usually just to find another dependency to integrate.”
I fear it’s JS development mindset in general. I mean, you start a new project in RN, you get 1200 NPM dependencies. You start work, and you get thousands of dependencies. All that piles up to a huge amount of code that has to be parsed on start up (no ahead of time compilation or JIT).
That is one of my pains with react-native and the JS-community. Their tooling sucks, because they use javascript for everything.
Having a NullPointerException/"undefined" in my code means I have to go hunt the bug for a couple of minutes. Having it in my buildtool means I my productivity drops to zero for an hour.
RN also keeps using deprecated and old version of android-buildtools.
Fun fact:
"NullPointerException" gives 2.47 million results on google.
"cannot read property of undefined" gives 3.71 million results.
(Background: I'm a Java, Kotlin and JavaScript developer, shipped an app using react-native for the Views only, but Kotlin for the business-logic. I also picked some fights with the RN-maintainers on github issues.)
Correct. Every React Native component actually renders into a native view, so on iOS if you use a View (RN) it maps to a UIView when React Native actually builds the UI.
Mapping to UIView is about the only thing that is “native” about React Native. My comment was about Native Script, which uses actual native widgets and concepts, such as controllers, animations systems, navigation, etc.
Could not agree more. There are certainly benefits to using React Native, especially when bootstrapping an app and you've already got a React shop, but once your app and user base gets larger it creates a serious barrier to actually taking advantage of the native platform and it's capabilities.
I think they're trying to say that the democracy is now worse because we have a leader who is lying to the media, threatening voting rights based on unsupported claims, silencing scientists from sharing publicly funded research, and is charging journalists with felony charges for covering protests against him.
How about the previous President who ignored the Constitution blatantly (4th Amendment anyone?) and continued the global surveillance of US Citizens without any due process (unless you consider Secret Courts one?), and lying blatantly about it in the first place? Does that count for anything?
A good precedent has already been set for this. The first iPhone got two major updates, iOS 4.0 being the first version that didn't support it. The 3GS added an extra year to the lifespan, launching with iOS 3.0 and only being left out of support for iOS 7. The 4S added even another year, recently having received the fourth major update of it's lifespan.
So yeah, while there is certainly some performance lost on a 4S running iOS 9, it's not nearly as bad as the original iPad running iOS 5, or the original iPhone running iOS 3. I imagine the 6S will easily be able to handle iOS XV.
Also noteworthy is that the only iPad not still receiving updates is the original model, meaning the iPad 2 has received the most major updates of any iOS device at five.
This is the dilemma I've run across over the past couple of years. Android devices have a much worse track record regarding official OS updates compared to iOS devices. But then on the flipside, when my iOS devices get older, I can't downgrade or install something more "lightweight" like I can with my Android stuff.
Maybe I'm just used to being able to repurpose old laptops and desktops with slimmed down Linux when they run current versions of Windows or OSX too slowly. All I know is that my original Nexus 7 (2012) is not getting the newest Android update while my iPad 2 (2011) is getting the latest iOS...
...but I want nothing more than to be able to put a third party ROM image on that old iPad or even downgrade it to an older iOS because while the Nexus 7 still works fine, the iPad running the latest iOS is practically unusable. Even reading books on it causes hangs and stutters. Task switching is miserable and trying to run more than one or two tabs in the browser is just masochistic.
I don't even care about jailbreaking or rooting or warranties or any of that. These things are both out of warranty and I own both so I accept the risks. But to this day, I still can't find any way to get something less demanding up and running on that iPad 2. I don't mind not having new features that require new hardware. I'd be happy with good performance and a simple set of apps (browser, email, calendar, e-reader, etc) as long as it didn't stutter and lag through it all.
If you are using an old version there are generally known security holes so while the snappier performance might be desirable I don't think it is a good trade off.
The iPad 2 is so slow on ios8 and newer that most people wouldn't actually want to upgrade, though [1]. Apple sold the iPad 2 until 2014 as a low-end model, so they can't really stop updates completely, but it isn't really usable.
I think there is a public image component to Ive as well. The image of Jobs' era at Apple is Ive and him running the show. As great as Tim Cook is doing in the CEO position, Ive is still seen by many as the remaining influence of Jobs. Regardless of his day to day responsibilities having him at Apple in some design role allows them to keep that perception. If he were to leave I think it will have a very negative impact on stock.
I really like Estimote, but it seems like they're selling premium hardware in a space that's racing to the bottom. Most beacons really don't need the temperature sensors or accelerometers. I finally got my nearables order last month, over six months after the first promised delivery date, and as great as those are ten dollars each is still a bit much IMO. Their solid SDK and developer relationships aren't going to matter too much if stuff like Facebook's beacons take off, making it so that businesses don't even need people to download an extra app.
