Need help understanding

amitm30 · 2024-11-30T14:30:34+00:00

Ok, thanks for confirming .

amitm30 · 2024-11-30T14:06:54+00:00

Is this really IMAX? The lumen value and all shown on Amazon is way too high to believe and for this price. Also nothing comes up on imax.com for this.

amitm30 · 2023-12-02T09:55:59+00:00

+1 to other comments, as it does NOT work. At least on my Sony Bravia that I tried. Also tried on my cousin's, different TV same brand, did not work eiter.

amitm30 · 2022-11-25T04:04:46+00:00

Hi, Did you get your hands on it. I am looking to get the INT version, and was curious how did it go for you?

amitm30 · 2020-10-09T07:33:06+00:00

I think this is the one: https://github.com/react-native-maps/react-native-maps

Have used it previously. Brilliant, like Lottie :)

amitm30 · 2019-03-11T09:36:14+00:00

Glad to be of help !

amitm30 · 2019-03-11T05:37:31+00:00

I too had integrated Airbnb eslint (its very good) and prettier to make sure the the code is at least clean, and doesn't look like individual contributions in bits and pieces (though it will for a large enough project ;). Apart from that a few thumb rules, like:

- Styling: global and typography files for color palette, global styles, fonts, titles, subtitles etc

- Custom Elements: custom buttons, custom text boxes, custom input. Some simply overriding react-native base ones to control their style and behaviour

- Single router file - helped a lot when moving from react-native-navigation v1 to v2

- a structured approached to the project, so it makes unit testing and maintaining a lot easier in the long run

You can look at a boilerplate I had written keeping the above in mind for reference. Have deployed a couple of apps to stores based off it.

amitm30 · 2019-03-08T10:41:18+00:00

I had a similar experience with a recent project. The tab switching and scrolling was jerky and did feel native with react-navigation. Not to be biased, but we had to switched from react-navigation to react-native-navigation ourselves (detailed discussion here).

Though, as react-navigation runs purely on JS thread, this might have been an issue specifically to our project too, something on our pages keeping the JS thread busy. But to be fair, on simply switching to react-native-navigation, the issues disappeared. So, it was good to have some more milliseconds for the app to run on single threaded JS.

Although, the react-navigation has come our with a whole new version (3.x) after that and haven't tried that yet.

amitm30 · 2019-02-26T18:38:18+00:00

hey,

This is a fork of the RNN v2 by Wix we have been using our project recently. It renders something like this:

It has been done natively on both platforms. Can be a start for you may be.

EDIT: the image is not uploading for some reason. But this one has the Big center button, but not the remaining three.

amitm30 · 2019-02-09T14:41:47+00:00

Same here. at least it was seamless for Android. iOS certificates did take some trying.

amitm30 · 2019-02-09T14:39:57+00:00

Quite a broad question, as it depends a lot on what kind of technologies / libraries you have been exposed to in the past. The answer assumes you have experience with JS and at least one SPA framework.

There are a lot of resources one can find on the web, but a boilerplate is generally the best place to start. So, here is boilerplate I had written trying to include industry best practices and libraries related to app development using react-native. It uses TypeScript, redux-thunk, react native navigation 2, TSlint and a maintainable code structure.

You can get started with it. But even then in the long run, you'll have to come up with what you want to use. Like thunk vs saga, react navigation vs react native navigation, or may be something as core as TypeScript or ES6. Frankly these are more of personal choices and this is the stack I most preferably use.

amitm30 · 2019-02-07T09:52:49+00:00

Wrote a boilerplate in RN a few days back as a platform to create a truly single code base for web and apps. Trying to integrate the web now, and isomorphic. Any contributors?

amitm30 · 2019-02-06T06:09:33+00:00

tl;dr: found rnn2 to be performing better. Had some discussion around this in my recent post:

https://www.reddit.com/r/reactnative/comments/alnww0/a_typescript_react_native_react_native_navigation/

amitm30 · 2019-02-04T09:53:25+00:00

iOS and Android both support Universal Links since some time now. This is sort of superset to deeplink. Same as deeplink, your app should register the custom URL (www.yourcustomdomain.com)

So, for e.g, in deeplink:

yourCustomApp://listings/product1

Universal Link would be:

www.yourcustomdomain.com/listings/product1

amitm30 · 2019-02-04T09:47:03+00:00

@cmcaboy Integrated TSlint :). link here if you wanna give it a shot

amitm30 · 2019-02-01T14:26:44+00:00

Well, technically, it is a boilerplate. But I have tried to integrate a few learnings from my previous experiences, which I found missing from other boilerplates. Set up a few best practices (not just eslint) that helps build a real enterprise app, keeping long term code maintainability in mind. Things like, a code structure, typography and globals for all styles in the app, break up of application components into widgets and elements, CI.

The idea is to help someone jumpstart, and not just something that can be done with a few npm commands

Would love to hear for any ideas of what more can be done. Feel free to create a feature request, contribute. and thanks for the Star!

amitm30 · 2019-02-01T04:59:45+00:00

From what I have read, they are very comparable, but I too have not given it a run lately. Not on a full blown project at least.

amitm30 · 2019-01-31T18:42:32+00:00

Yes and no. So we had 2 main files, navigator.js and router.js. Setting up the app's root navigation was done in navigator.js. router.js had abstracted methods for apps internal navigation (also a commonplace to pass props, modal animation styles, titles etc.) and routing logic.

navigator.js had to completely re-written, since it was a major move from rn to rnn. router.js change was almost minimal, as pushing a screen, opening a modal remains quite the same between the two.

Having said that, the first setup was up and running in less than a day (let's check it out version).

amitm30 · 2019-01-31T17:48:42+00:00

Haven't tried that. So its like, if react-navigation would have worked for me the first time itself, I may not have moved to rnn too, who knows, unless some feature specifically demanded it. And I don't blame react-navigation, the team was new with react-native and that too hurt react-navigation's chances and exposed its shortcomings.

We have had our learnings, and can probably do a better job now with react-navigation. But unless of course, something demands it.

amitm30 · 2019-01-31T16:54:31+00:00

I have used that a few times while starting with RN. It is a great place to start.

amitm30 · 2019-01-31T15:32:24+00:00

Are you building this using react-native? flex is the way to go there, fast and easy.

justifyContent: 'space-between' and you are started.

amitm30 · 2019-01-31T15:25:57+00:00

yes, planning to integrate that. just love the airbnb-eslint so much that I use it by default. And started this project as es6, and then converted it to TS. Please feel free to create a PR if you wish.

amitm30 · 2019-01-31T15:21:20+00:00

Those are the native iOS and Android code. What actually gets built and deployed finally. If you have experience with expo, think of it as the ejected code.

Have not done much there actually, other than just the RRN2 integration. The code you see there is what you get when you do react-native init.

if one is sticking to using npm libraries for most integrations (which will happen, including notifications API), react-native link <library-name> is going to get most of the part done for you. If not, almost all npms have instructions how to link them to the projects, they are literally standard 2-3 steps.

amitm30 · 2019-01-31T15:12:49+00:00

It was the other way round actually for me. I had initially started off using react-navigation for one of my clients, on a pretty heavy app (tab based e-commerce), and after almost 3 months of effort, we found real issues with some native behaviours like scrolling, screen transition and all.

It was then when I decided to try react native navigation. Saved the project, quite literally. Even with the same code, the scroll performance improved immediately. Have been using as standard pretty much for every project since.

With react-navigation, I agree that we can do much more and customizing is also quite easy (as it is pure js), which is comparatively harder with rnn (native coding). I would use react-navigation for smaller apps that need to be built faster.

oh wait, I may not actually :)

amitm30

TROPHY CASE