they're used to gather information about the pages you visit and how many clicks you need to accomplish a task. Royale will be the next step of abstraction and structured. May not be reused without permission, Flex Business Application converted to Apache Royale, Dev Conversation about Emulation Components. This comparison is plain wrong if you care about app size. Jewel themes support up to 12 colors, light/dark, and flat/normal modes. Native dev approach is definitely a king. And it would most importantly open Royale up for investors. https://emberclear.io/bundle/broccoli.html, Is it possible to get this updated? §
they're used to log you in. What we can learn from Airbnb is that you can benefit from different dev approaches at a particular time. Choose what works best for you as an individual and/or your team. Maybe you want to add that to the list or update the 2.0.3 entry from above? Otherwise, you’ll have to spend time on hiring experts for two (or more) platform-specific teams. Find code samples for common app scenarios on the NativeScript Marketplace. Just what I was looking for. This allows them to leverage advanced functionalities (memory management, complex networking, etc.). @keyboardSmasher I think sizes matter a bit more than you give it credit for. JQuery is still a fantastic tool that weights less than the other frontend frameworks.. We’ve worked extensively on open/shared source code initiatives in the past, and as a commercial consultancy firm it works best for us
I fear the target market of Royale--Flex Devs who want to build HTML5 applications--moved on many years ago. I think this is a must, don't
Due to that, they both allow you to speed up the pipeline. I think there’s a middle ground where some of
I think it's this implication that is wrong. I don't know. The average connection speed for Internet users worldwide, not just among these 50 countries, but all countries, is an average of 1.8 Mbit/s. So my approach almost has to be “on-demand” mixed with some prioritization. If you wanted to just ship your Flex application as-is, then we can just
Correct me if I'm wrong. To deliver a mobile experience to your users, building a native app is not the only option. Thanks for clarifying this a bit more Carlos, it is an interesting topic for me as the company I work for is in some trouble and if I should find a new job (unsure at the moment) then it can be that I need to use
Browsers do a great drop masking network issues where they can, but if your "critical" bundle is large enough to require two, three, or more TCP round trips, your high-percentile render times will spike up accordingly. Reply | Threaded. All the rest discloses many differences between cross-platform vs. hybrid app development. What a hybrid approach can attract with is low price and high dev speed. All users regularly experience transient latency spikes, dropped packets, and so on. To some extent, progressive web apps or PWAs resemble hybrid ones. Native is not a must for the mobile experience. And do not expect a fast TTM unless your developers are supermen:). ViewStack), we’re more inclined to just create a very simple specialisation of a ContainerBase to do this for us rather than to use the emulation component which has other dependencies that would be pulled
I would agree with Alex about the contribution model and how this would work; we’re a slightly odd case though as we’re at consultancy firm (at least, the bit of Harman that I work for) and so we
BorderContainer) but some of the other functionality could be stripped back/removed. The developers love the maturity of Flex. https://emberclear.io/bundle.html, I love this list! And the cost is the key distinction of native vs. hybrid app development. Yishay contacted me to tell me about the emulation components built into the Apache Royale. Thank you, Nicolas Granon > -----Message d'origine----- > De : Harbs [mailto:firstname.lastname@example.org] > Envoyé : mercredi 4 octobre 2017 15:37 > À : email@example.com > Objet : Re: [DISCUSS] project vs. project name > > Makes sense to me. There are some use cases that claim they managed to achieve native performance, but these are perhaps… less than honest:) TTM?
Not sure we need a new company (we provide consultancy services around Flash/AIR/Royale..!) I expect that as me and others can get real apps written in Royale, people will want to enter
Please allow me to use the number in my presentation! think there’s a middle ground where some of the commonly used components are emulated fully (e.g. Instantly share code, notes, and snippets. yes :D I do wish the team luck, they have some of the smartest people I had the privilege of knowing. Yet, you can still access the app on the home screen. IMO, we need more contributors first, in order to make the rest happen, and the best source of these new contributors are the folks using Royale. Can you add preact and inferno please ?
Users get better scrolling, dynamic animations, and other appealing elements. 0kb is hard to beat. And it would most importantly open Royale up for investors. @PhilippMeissner probably not, but feel free to fork and do that. https://cost-of-modules.herokuapp.com. So coming back to the specific points raised by Ulrich: It's an interesting project though, and one I hope will continue to develop and improve. recording engineer, and I love old school style adventure games. Coding; Los Angeles Campus. Once your product has been marketed, you might consider evolving it into a native app with time, budget permitting. Such technologies might be AngularJS or React. features to Royale. Instead, those of you who are stakeholders because you have Royale apps will
I wonder if you're using import and only import 'what you need' at the bare minimum to run a single page what the file sizes are then. Documentation is another area I think we could help
Definitely agree with this – but tricky to do without more test cases and also real-world application that find out about the bugs. Work towards 1.0 release. I think is funny. Everyone else contributes when they can. The native code implements some sensors whenever you need them to the fullest extent. It seems like Angular 2 is much better than the rest, as it has more support, easy to learn and more configurable. Also, I don't think it's accurate to include the examples with the Angular 2 + the entire RxJs library, the entire RxJs API is quite large and apps just need to include the functions they use, which is usually a much smaller subset of the entire library.
I thinks is no more what's better, I'm sure each one has its own pros and cons. May we get an update on the size of each framework now? Also probably helped if we can improve the “getting started” documentation and demonstrating how to get up and running using the various IDEs.. Not sure we need a new company (we provide consultancy services around Flash/AIR/Royale..!)
It is the best option if you do not think much of UX and performance. I don't think a compiled list of sizes pulled from public CDN could be wrong in a way you presented. In my company, since
Consultancy companies shell what is hot, since is what clients demand. With NativeScript and Angular, a single code base (and skillset) can be used to create web apps and native mobile apps with 100% native performance and power. But I do think that we probably want different > release packages. Riot: 24K Nov 7 15:48 riot.3.7.4.min.js, 10.3K gzipped and others.