{"id":967,"date":"2019-07-05T20:27:17","date_gmt":"2019-07-05T20:27:17","guid":{"rendered":"http:\/\/fluentreports.com\/blog\/?p=967"},"modified":"2019-07-06T16:55:51","modified_gmt":"2019-07-06T16:55:51","slug":"nativescript-and-fortnite","status":"publish","type":"post","link":"http:\/\/fluentreports.com\/blog\/?p=967","title":{"rendered":"NativeScript and Fortnite"},"content":{"rendered":"\n
\"\"<\/figure><\/div>\n\n\n\n

Isn\u2019t that an interesting title \u2013 I wonder if you can guess how I plan on tying the two together! Can we all say Click Bait<\/em>! Stay tuned, and we will show you how I combine both of these into one blog post...<\/p>\n\n\n\n

Now many of you know\nthat NativeScript is 100% open source. I can take NativeScript and\nbuild the entire stack locally on my computer and never deal with\nProgress again, if I were to so choose. This is awesome from the\nstandpoint that I am not technically stuck (*1) if I need to fix some\nissue. Many of the technology stacks in the past you could get to a\npoint, and then if the issue was lower in the stack you were totally\nstuck. In my career I\u2019ve run into this several times; and it\nreally sucks when you can\u2019t fix the issue because it is a issue in\na lower part of the framework where you can\u2019t get any access to it.\n In this case; we have full control over everything if and when we\nneed it, so we are is a great position moving forward if using this\nstack.<\/p>\n\n\n\n

So, the question I\nhave seen around; and even had myself in the past was: Since\nNativeScript doesn\u2019t make any money, how can Progress possibly\ncontinue to pay to keep it going? What is their business plan to\nturn a profit, and when will it be cut off? \n<\/p>\n\n\n\n

Seriously; common sense says; if a product doesn\u2019t make money after a couple years; a company will discontinue it. How many projects has Google canned that is making money; but not making as much money as they wanted to continue it? So, if the product has no real way to make money long term; then why would they keep it?<\/p>\n\n\n\n

Yes, it does have a\ncouple minor revenue streams, like paid support; but even the paid\nsupport probably doesn\u2019t actually fully even pay for just the\nsupport techs that do all the awesome support for NativeScript. So\nbasically NativeScript does not make any money directly. On paper;\nit looks like it is probably just burning money... \n<\/p>\n\n\n\n

So why would\nProgress spend so much money to continue enhancing, and maintaining\nit, for a product that will never actually turn a profit??? Then\nwhat are our risks as the community that they will pull the plug\ntomorrow when they finally figure this out???<\/strong><\/p>\n\n\n\n

Well rest assured; I\ndon\u2019t believe it will discontinued any time soon. First; I would\nbe totally shocked if most of NativeScript development costs are not\nwritten off as a very nice tax liability (*2). Smart companies have\nmoney pits in certain area for key reasons, one of the biggest is\ntaxes. The other interesting thing is it is not really just a\nnormal<\/strong> money pit used just for tax liability reasons. \n<\/p>\n\n\n\n

NativeScript is the\nAdvertisement<\/strong>. NativeScript is not a product, in that sense\nto Progress \u2013 it is a significant way to get you (the developer) to\nuse Progress services. So just like some large company might pay\nmillions of dollars in advertising; per year to try and reach you. \nProgress is doing the same thing \u2013 but instead they are actually\ntargeting it specifically at developers. Virtually every dollar of\nadvertising is being spent on developers. Who is a large part of\ntheir market target; well us developers! So it is an extremely well\ntargeted advertisement, much better than you can do with any adwords\nscheme you can find!<\/p>\n\n\n\n

Changing this point\nof view, completely changes the entire narrative of why NativeScript\nexists and its continued long term viability. It is no longer just<\/strong>\na money losing venture of Progress. It is an significant\nadvertisement to get you to use all the other Progress services. \nThis is a critical point to understand; as this underpins the whole\nreason why NativeScript should continue to exist for the foreseeable\nfuture.<\/p>\n\n\n\n

Since NativeScript is very much like Fortnite (see told you I would work it in!). They hand out the awesome 100% free game. And which game company has been just raking in the money (like 2.4<\/strong> BILLION<\/strong> in 2018 alone) from a single free game? And if anyone follows Fortnite; you will know they are constantly improving it. However, they get you on all the \u201cextra\u201d attached revenue streams. Yes, you can play Fortnite 100% free and never spend a dime and even continue playing all the cool game modes that keep getting released. <\/p>\n\n\n\n

You can also use\nNativeScript, create awesome apps and never actually spend a dime\nwith Progress. Which is actually what the majority of the community\ndoes; but all Progress needs is a very small percentage of the\nNativeScript users to use its payed services and NativeScript ends up\ncausing a major profit for them. \n<\/p>\n\n\n\n

As some examples; to\nshow how this works\u2026 Progress owns NativeScript, and say you want\nsomeone to build you an app, who is your first stop? (Especially if\nyou are a large company!) You might see a nifty services page on \nProgress\u2019s site \u2013 you contact Progress. But they do not\nactually do the contract work. They actually sub-contract it out to\nothers; and take a hefty cut for that privilege. This works well for\neveryone involved. Or perhaps you are a independent developer;\nSidekick, cloud builds, attend the conferences? All revenue\nstreams. Larger companies; secure data storage, chatbot, ai, etc. \n Progress offers many of these \u201caddon\u201d services; and all of\nthem have fully working integration's with NativeScript. So any\ndevelopment by a enterprise class company has a large chance of\nstarting and choosing to stay with the owners of the NativeScript\nstack and paying for that privilege.<\/p>\n\n\n\n

In other words; Progress is brilliant \u2013 they have managed to figure out how to take the same model used for Fortnite and use it on developers. So hopefully this reassures everyone that NativeScript should have a long life ahead of it. (*3) <\/p>\n\n\n\n

Well played,\nProgress!<\/p>\n\n\n\n

\n\n\n\n

Notes:<\/h2>\n\n\n\n

*1 \u2013 I am not\nstuck; in that I can fix my own copy of the code and deploy the app. \nThis does NOT mean that Progress will take your patches and fix the\nmaster so that it is fixed in the next version(s). It just means you\ncan fix it in your copy\u2026<\/p>\n\n\n\n

*2 - Progress is a\nmulti-national company; so they have taxes in multiple countries \u2013\ndifferent countries have different laws; but typically losses in one\nbusiness unit can be used to write off tax gains in other units. So\nthe \u201cpaper\u201d loss of NativeScript offsets revenues from the other\nparts of the company, and so it then lowers some of their tax burden\nin probably several countries.<\/p>\n\n\n\n

*3 - I am not a employee of Progress or Telerik; nor have I ever been, so this is all based on the know facts. However, this matches all the facts to a T. So, it is my strongest belief based on all public data available; that this is why NativeScript exists and will continue to exist. It also explains why Progress was willing to continue to sink million of dollars into NativeScript; and also purchased things like Kinvey for 49 million dollars. <\/p>\n\n\n\n

\n\n\n\n

Please note all companies names, Logos and products are owned by their respective owners and convey no endorsement of any content or other products in this post. <\/p>\n","protected":false},"excerpt":{"rendered":"

Isn\u2019t that an interesting title \u2013 I wonder if you can guess how I plan on tying the two together! Can we all say Click Bait! Stay tuned, and we will show you how I combine both of these into one blog post... Now many of you know that NativeScript is 100% open source. I… Continue reading NativeScript and Fortnite<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"categories":[15],"tags":[137,16,138],"class_list":["post-967","post","type-post","status-publish","format-standard","hentry","category-nativescript","tag-fortnite","tag-nativescript","tag-progress","entry"],"_links":{"self":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/967","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=967"}],"version-history":[{"count":3,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/967\/revisions"}],"predecessor-version":[{"id":982,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/967\/revisions\/982"}],"wp:attachment":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=967"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=967"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=967"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}