Podcasts about android sdk

Your medical records don't make pleasant bedtime reading. And not only are they inscrutable—they're often mutually (and deliberately) incompatible, meaning different hospitals and doctor's offices can't share them across institutional boundaries. Harry's guest this week, Ardy Arianpour, is trying to fix all that. He's the co-founder and CEO of Seqster, a San Diego company that's spent the last five years working on ways to pull patient data from all the places where it lives, smooth out all the formatting differences, and create a unified picture that patients themselves can understand and use.The way Ardy explains it, Seqster “smashes the data siloes.” Meaning, the company can combine EMR data, gene sequence data, wearable device data, pharmacy data, and insurance claims data all in one place. The big goal guiding Seqster, he says, is to put the patient back at the center of healthcare.Please rate and review The Harry Glorikian Show on Apple Podcasts! Here's how to do that from an iPhone, iPad, or iPod touch:1. Open the Podcasts app on your iPhone, iPad, or Mac. 2. Navigate to The Harry Glorikian Show podcast. You can find it by searching for it or selecting it from your library. Just note that you'll have to go to the series page which shows all the episodes, not just the page for a single episode.3. Scroll down to find the subhead titled "Ratings & Reviews."4. Under one of the highlighted reviews, select "Write a Review."5. Next, select a star rating at the top — you have the option of choosing between one and five stars. 6. Using the text box at the top, write a title for your review. Then, in the lower text box, write your review. Your review can be up to 300 words long.7. Once you've finished, select "Send" or "Save" in the top-right corner. 8. If you've never left a podcast review before, enter a nickname. Your nickname will be displayed next to any reviews you leave from here on out. 9. After selecting a nickname, tap OK. Your review may not be immediately visible.That's it! Thanks so much.Full TranscriptHarry Glorikian: Hello. I'm Harry Glorikian. Welcome to The Harry Glorikian Show, the interview podcast that explores how technology is changing everything we know about healthcare. Artificial intelligence. Big data. Predictive analytics. In fields like these, breakthroughs are happening way faster than most people realize. If you want to be proactive about your own health and the health of your loved ones, you'll need to learn everything you can about how medicine is changing and how you can take advantage of all the new options.Explaining this approaching world is the mission of my new book, The Future You. And it's also our theme here on the show, where we bring you conversations with the innovators, caregivers, and patient advocates who are transforming the healthcare system and working to push it in positive directions.If you've ever gotten a copy of your medical files from your doctor or hospital, you probably know these records don't make pleasant bedtime reading. They aren't designed to be clear or user-friendly for patients. In fact, it's usually just the opposite.The data itself is highly technical. And on top of that, there's the inscrutable formatting, which is dictated by whatever electronic medical record or “EMR” system your provider happens to use. But the problem isn't just that EMR data is incomprehensible.It's also that different EMRs are often incompatible with each other.So if you're being treated by multiple providers, it can be really tricky to share your data across institutional boundaries. That's why medicine is one of the last industries that still uses old-fashioned fax machines. Because sometimes a fax is the only way to send the data back and forth.But my guest today is trying to fix all that.His name is Ardy Arianpour, and he's the co-founder and CEO of Seqster.It's a company in San Diego that's spent the last five years working on ways to pull patient data from all the places where it lives, smooth out all the formatting differences, and create a unified picture that patients themselves can understand and use.The way Ardy explains it, Seqster quote-unquote “smashes the data siloes.” Meaning, the company can combine EMR data, gene sequence data, wearable device data, pharmacy data, and insurance claims data all in one place.The big goal guiding Seqster, according to Ardy, is to put the patient back at the center of healthcare.At the moment, however, consumers can't sign up for the service directly. Seqster's actual customers are players from inside the healthcare industry. For example, a life science companies might hire Seqster to help them make the experience of participating in a clinical trial more user friendly for patients.Or a health plan might use a Seqster dashboard to get patients more involved in their own care.Seqster did let me do a test run on my own medical data as part of my research for this interview. And I was impressed by how quickly it pulled in data that normally lives in a bunch of separate places. I'm hoping Seqster and other companies in this space will continue to make progress.Because, frankly, I think poor patient access to health data and the lack of interoperability between EMRs are two of the biggest factors holding back improvements in healthcare quality.If we can finally get those two things right, I think it can help unlock the data-driven healthcare revolution that I describe in my new book, The Future You. Which, by the way, is out now in paperback and ebook format at Barnes & Noble and Amazon.When we spoke back in September, Ardy and I talked about better EMRs and many other things. And now here's our conversation.Harry Glorikian: Ardy, welcome to the show. So, it's good to have you here, and you know, for everybody who doesn't know your story and the story of the company, I'd love to, you know, start covering some basics like, you know, the when, the what, the how, the why. What's the founding story of Seqster and what was the problems that you were really trying to go out there and solve when you started the company in 2016?Ardy Arianpour: Thanks so much, Harry. Always been a fan. I think we've known each other for quite some time, but it's been a long time since we've ran into each other since the genomic and precision medicine days. So great to see you. I hope you and your family are well and yeah, look, Seqster is super special and there's a secret story, I guess, that never has been told. It really starts way beyond 2016 when I founded the company. So I spent 15 plus years in DNA sequencing, next gen sequencing genomic market. And during that time in the 2000s to early 2010s, I was fortunate enough of being part of some amazing endeavors and organizations that allowed my team and I to take some risk. And when you take risk, when you're in biotech, pharma, precision medicine, genomics, bioinformatics, you learn new things that most people don't learn because you're you're you're, you know, trailblazing, I guess you could say. And we were able to do that back with one of my old companies where we were able to launch the first clinical exome test, launch the first BRCA cancer panels, launch the first next gen sequencing panels in a CLIA lab. Ardy Arianpour: And then, you know, it wasn't about the testing. It was all about the data, and we didn't realize that till later and we kept on seeing that wow genome data is really only one set of all the other data pieces, right? I think the genomics folks, me being a genomics guy, I guess you could say, for a decade and a half, we're so forward thinking that we forget about the simple things within science, and we never really thought, Oh, collect your medical data and pair it with your genomic data. We never really thought there would be a wearable out there. That data was going to be siloed, too. We never thought there was going to be, you know, many different medical devices and instruments that would be Bluetooth and sensor enabled, where there would be data that would be siloed. Claims data, pharmacy data. Never even crossed our minds. So, you know, when you put this all together, my inspiration with Seqster was actually really simple. And when I founded the company, I wanted to combine the genomic data with your EMR medical data as well as your wearable data, because in 2016, the tailwinds of those other, you know, services was really taken off.Harry Glorikian: Right. Totally understand it. And you know, as we were talking about before I hit record, it's like it was funny because I was just talking to another company that's working on NLP and they're able to look at, you know, papers and see drugs being used in different, you know, medical conditions. And then they figured out, well, they needed to tap into the unstructured data of a medical record to really, like, add the next layer of value to it. So, you know, there's a lot of activity going on about there. But how do you guys, how do you, how do your co-founders, you know, Zhang and Dana play into like the science, the technology and what's the sort of angle that you guys have taken to solve this problem? Or what's your idea on how to fix it? I'm not saying it's been solved yet, because that would be a Herculean task in and of itself. But how are you guys approaching it that? Is a little different than the. You know, maybe any any of your other you would you would consider anybody else out there, the working on this?Ardy Arianpour: Yeah, look for us we spent a lot of time understanding the power of data. But how what makes Seqster different is no one knows the power of the patient better than us. We've spent time with our platform with, you know, tens of thousands of patients: rare disease patients, oncology patients, parents, autoimmune disease patients, patients that have that are seeing functional medicine folks. Patients that were having issues sharing data through telemedicine, clinical trial patients. All these sorts of patients are very different. At Seqster we focused on putting the patient at the center of health care in order to smash all the data silos from their medical institutions to their wearable technology that they wear to the DNA testing that they get and even maybe a COVID test or a vaccine. How do you bring a 360-degree patient view? And you know, you tried the system, so I think you got a small teaser of how we can do that and we've really cracked this large problem. It is Herculean, I believe, and a lot of people believe because it's interoperability, it is the number one problem in all of health care.Harry Glorikian: Yeah, I mean, I had the pleasure of trying it and imported my data and was able to see, you know, individual pieces. I mean, I made some suggestions on what might make it easier for me to hone in in different areas, right, and have the system highlighting different things. But I guess each data stream is being brought in separately and then at some point you're going to create a master dashboard above it, because now each one is separate from when I go into each record, right, When I go into my medical record, it gives me one set of data with my lab results and everything else and the notes, and then it pulls in my wearable data separately that I have to look at, right? So you've got to look at it separately. It doesn't. Then I guess the next step would be creating a master sort of view of how everything would look in a sort of I don't want to say integrated, but at least a timeline view of the world. But. You know, following up on the the sort of the what question, you know, how do you sort of combine data from different EMRs, tests, apps, devices in a sort of scalable, repeatable way? I mean, it seems like to date, that's been a hugely manual process, and I can imagine you could figure out every provider's ontology and then create a table that shows what's equivalent to. And but you know, there's got to be sort of a translation scheme that would be required that that provides some constant readjustment as the main providers tweak and evolve their own systems, right? Because if the provider is tweaking their system, your system has then got to adapt to changes that are happening in that end. So how are you guys managing all that craziness?Ardy Arianpour: Yeah. So I think it all and you hit on so many points, I'll try and cover them if I remember them all. Look, the number one thing for us is we can connect to any data source. It doesn't matter. And you saw it. And just before I continue, just tell the audience how fast, how fast, how long did it take for your data to be populated after you connected it?Harry Glorikian: Oh, it was. I mean, yeah, as soon as I created it, I could see that it was, you know, it was digesting and then populating. And, you know, I was just I was watching it as a matter of fact, when I was on the phone with your person, that was helping me. Yeah. At first I said, Oh, it's not there. And then a couple of seconds later, I'm like, Oh no, it's showing up, right? So it was happening in, I don't want to say real time, but it was happening as as we were watching it evolve, right? It was sort of it was. It was almost like watching time lapse.Ardy Arianpour: And that's actually a great way. That's a great way to actually describe it. We created the time lapse of all your health data. Now let's get to the what and the how. So we connect to any health data source. The patient is fully in control. You own your data, you control it. It's all consented by you. We don't own your data and we connect to every single medical record. And that's huge that we've achieved nationwide coverage. We didn't know what data you have, but we're you're able to connect to it. Why? Because our team, which our engineering team gets all the credit for six years now, almost since founding of the company we have written, I don't know, seven million lines of code, that standardizes and harmonizes all of the ICD 9, ICD 10, SNOMED codes and every single lab result to every single wearable terminology, from biking to cycling to, you know, you name it, VitaminDB, you know, characterized in 40 different ways. You know, we're harnessing data to improve patient lives at scale. We built it for scale because you can't do it by the traditional method of just faxes and PDFs. Now, you know, being able to do that is not a bad thing.Ardy Arianpour: We can bring that service into our platform as well. It's already integrated, but that type of service takes 30 to 60 days and it's static data. It's not real time right now. If Harry goes, I don't know, you go on a bike ride and you fall and you go to the E.R. and you had whatever data connected automatically in your sister portal, it'll be populated without you even touching Seqster. That's how our real time data works and another way that we're totally differentiated than anything else in the marketplace. I was never a fan of API businesses because they're just data in data out. I truly wanted us to create a patient engagement platform, a PEP right, or a patient relationship management system, what I call a PRM instead of a CRM. And that's what we created with Seqster. So that is beyond an API, beyond just data. We're visualizing the data, as you saw. We really nailed the longitudinal health record or the individualized health record. And I think it's, I always say this, health data is medicine. The reason why it's medicine is because our platform has saved patient lives.Harry Glorikian: Ardy, how do you, how are you handling the free form notes, right, because I noticed that I could look at all my notes, but they weren't necessarily, it wasn't pulling from the note and sort of making sense of it. I mean, I could look at all of it and it was all in one place. But the the system wasn't necessarily processing it, sort of. I was talking to Jeff Felton from ConcertAI and they do a lot of sort of, their big thing is the NLP that sort of tries to choose chew through that, which is not trivial, you know, yesterday today, context matters in health care.Ardy Arianpour: Yeah. Look, if we created the the the Tesla of health care, let's just say, right, we're we're changing the game. From static data to real time data. Ok. Well, you're talking about is, are you going to create a helicopter as well? Right, OK. And all right. So, no, we're not going to go create the helicopter. Is there going to be an electric helicopter by Tesla? There's no market for that, right? So that's why they're not doing it now. I'm not saying there's not a market for NLP. It's just the fact that we'll go ahead and partner with a third party NLP provider. And we already have we have like four of them and they all have their strengths and weaknesses because it's not a one size fits all thing. And you know, we can already run OCR, you know, over the free text and pull certain ontology information out. And then, you know, when you partner with an NLP company, once you have a system that can capture data, you could do anything. So people always ask me, Are you going to get into AI? It's just the buzzword. There's a million A.I. companies. What have they really done right in health care? It's not really there. Maybe for imaging they've done some things, but it's more of a buzzword. AI only becomes valuable if you have a system, Harry, that can instantly populate data, then you can run some great artificial intelligence things on it. So NLP, AI, OCR, all those things are just many tools that can add. Now, in your experience, you only got to see about 5 percent of the power of Seqster, and that probably blew you away, even though it was five percent of the power. Because you probably never -- I don't know, you tell me, have you ever been able to collect your data that quickly? It took, what, less than a minute or two?Harry Glorikian: Yeah, well, thank God, I don't have a lot of data. So, you know, just when I tap into my my health care provider, you know, my data is there and it's funny, I always tell people, being a not exciting patient is a really good thing in one way, and it's a really bad thing because you can't play with all the data. But you know, like even when I did my genome, it's an extremely boring genome.Ardy Arianpour: My question is it's not about it being exciting or not, because thankfully you're not a chronically ill patients. But imagine if you were and how this helps, but take a step back. I'm just asking the speed, yes, and the quality of the presentation of the data that seeks to you. It was less than what hundred seconds?Harry Glorikian: Yeah. Well, it was very quick. And I've already it's funny because I texted my doctor and I was like, I need to talk to you about a couple of these lab results that look out of out of norm, right? And they weren't anything crazy. But I'm just curious like, you know, how do I get them in norm? I'm just I'm always trying to be in in the normal band, if I can be.Ardy Arianpour: So it's interesting you say that because as a healthy individual. You know, and even a chronically ill patient, it doesn't matter. The best way to actually QC data is through visualization, and this is what this is. That's foundational to interoperability. So we hit on semantic and structural interoperability with our, you know, backend engine that we've created to harmonize and standardize the data. We built many different types of retrievers and then we parse that data and then it's standardized and harmonizes it. But that visualization, which some people call the Tableau of health data, you know that we've created when they see it, is really, we got to give the credit to the patients. We had so many patients, healthy ones and unhealthy ones that told us exactly how they want it to look. We did this on the genomic data, we did this on the wearable data. We did this on the medical device data and we have some great new features that can superimpose your clinical data with your fitness data on our integrated view and timeline.Harry Glorikian: Oh, that? See, now that would be, you know, another level of value, even for a healthy patient, right to be able to see that in an integrated way. I made a suggestion, I think that when a panel shows up is. You know, highlight the ones that are out of Norm very quickly, as opposed to having to look at, you know, the panel of 20 to find the one that's out of whack, just either color them differently or reorient them so that they're easier to find. But those are simple changes just from a UI perspective. But so. How would you describe that that Seqster creates value and say translates that into revenue, right? I'm just trying to figure out like, what's the revenue model for you guys? I know that you're I can actually, I'm not even sure if I can sign up for it myself. I would probably have to do it through a system if I remember your revenue model correctly. But how do you guys generate revenue from what you're doing?Ardy Arianpour: Yeah, I'll share another secret on your show here from the founding of Seqster. My dream was to empower seven billion people on our little mothership here called Earth to have all their health data in one place. And I had a direct to consumer model in 2016. The market wasn't really ready for it, number one. Number two, it was going to cost $500 million worth of marketing to just get the message out for people to know that it exists. So long story short, in 2016, you know, when I founded the company, not that many people wanted to talk to us. They thought we were just like nuts to go after this problem. 2017, we got some calls from some investors, we raised some great seed funding after I personally put in some money in in 2016 to get the company going. And then in 2018, I got a call from Bill Gates and that was when everything changed. Bill called and wanted to meet in person, I was supposed to get 30 minutes with him. And the reason why he called is because our first beachhead was with Alzheimer's patients. My grandmother, both my grandmothers, passed away due to Alzheimer's disease. Both my maternal and paternal grandmothers and being a caregiver for my mom's mom and being very close to her since she raised me, I learned a lot about a multigenerational health record, so I actually filed patents in 2016 on a multigenerational health record because I wanted to have my grandma's data, my mom's data, my data, and be able to pass it on to research as well as to generations down my family.Ardy Arianpour: Long story short there, Bill gets all the credit for telling me after I showed him our platform, "You got to take this enterprise. You guys built something that Google Health failed at and Microsoft Vault Health Vault failed at." And it's funny we're talking about this. Look, Google just dismantled their health division again. Why? Because tech companies just don't get it. They have a lot of money. They have a lot of power. They've got a lot of smart people. But they they they don't know where, I'll give you an example. It's like a tourist with a lot of money coming into a city. You don't know where the really good local bar is, right? Why is that? You don't know where the really good, you know, slice of pizza is. You're going to go to the regular joints that everyone finds on TripAdvisor and whatever. You know your friends told you, but if you're a local, you know where to get the authentic cocktails and the authentic, you know, drinks and food. Why? Because you've lived and breathed it in the city. So we've lived and breathed it right. And so we know what not to do. It's not about knowing what to do in health care or in genomics or in biotech. It's actually knowing what you shouldn't be doing. Yeah.Harry Glorikian: And knowing I got to tell you, there's some problems where I'm like, OK, I know exactly who to call for that problem, because there aren't, you know, they're not falling off trees in that particular problem. There's a small handful of people that understand that problem well enough that they can come in and sort of surgically help you solve that problem. And you can have all the money in the world and have all the smart people you want. Doesn't mean they're going to be able to solve that particular problem, especially in health care, because it's so arcane.Ardy Arianpour: And it's getting, you know, this is a problem that is growing like cancer, interoperability. Just on this 20 minute conversation with you it has grown by hundreds of millions of dollars. Do you know why? Because data is being siloed.Harry Glorikian: Yeah. And I think, look, I've always I've said this on, you know, whatever show or and I've actually I've written letters to Congress. You know, I think this this needs to be mandated because expecting the large EMR companies to do anything is a waste of time. They're not going to do it on their own if their feet are not put to the fire and it changes. And honestly, I believe that if anything will stop the innovation of health care or slow it down is the EMR systems. You know, if you don't have the data, you can't do the work.Ardy Arianpour: Absolutely. But you know what people don't understand. And not to go off that tangent, but I'll get back to the business model in a second to answer that question because I just recalled in my mind here that I didn't answer that. Look, people don't understand that at least the EMR companies, even though they're like Darth Vader, you know, they needed. They've put some foundation there at least. If that wasn't there, we would be in a much worse situation here, right?Harry Glorikian: Correct, but if Satya Nadella hadn't really changed Microsoft, really redone it right, it wouldn't be the company it is now, and I think they [the EMR companies] are just back in the dark ages.Ardy Arianpour: Of course, I totally agree. I'm surprised, actually. Microsoft, as an example, didn't come up with their own EMR system and launch it to the hospitals to go, compete with the servers and all scripts and Epics of the world. If I was Microsoft, that's what I would do. I would have enough money in power, know exactly what to do. I would take a system like Seqster and I would explode it in a good way and be the good guys and have it completely open source and open network. But that's a whole cocktail conversation if anyone's listening on the on the podcast that wants to talk about that. Give me a call or shoot me an email or find me on LinkedIn.Ardy Arianpour: Let me go back to the business model real quick so people understand. So direct to consumer was what I wanted to do. We built it for the consumer, for the patients. It was the smartest and dumbest thing I ever did. Let's go to why it was the dumbest thing first, because it was really, really hard. It was the smartest because we would not be where we are today. You wouldn't have called me to talk on your podcast and all these other great, you know, amazing people that want to hear about how we're, you know, cracking the code on interoperability now and changing the health care system, changing clinical trials, changing decentralized trials with our system.Ardy Arianpour: Why? Well, it's because our system was built by patients. Right, and so it's a patient centric, real time, real world data platform that layers in engagements for both the providers, the payers, the pharma companies and any other enterprise that white labels our platform. We have both iOS and Android SDK and Web available. It gets fully branded. We're the Intel Inside with the Salesforce.com business model. It's a Software as a Service service that we offer to enterprises. Patients never pay for the service. And we do give VIP codes to chronically ill patients and VIPs, you know, journalists, podcasters and to be honest, anyone who emails me that wants to try it. I've been always giving on that. That costs us time and money, and I'm happy to do it because it's my way of giving back to the community and health care because I know our team and I have built a system that have saved lives. It's been covered by the news multiple times.Harry Glorikian: So, so in essence, a large provider comes, buys the access to the system and then offers it to its patient population to utilize to aggregate all this information, right? How can the platform stay patient centric if the patients aren't directly paying for it?Ardy Arianpour: Ok, very simple. All of these enterprises in health care, whether that's Big Pharma, right, or Big Oayer from Pfizer to Cigna, to United Healthcare group to Humana to even Amazon, right, to other tech companies, they all want to go down a patient centric way. It's just what's happening. You know, I've been talking about this since 2016 because we pioneered patient centric interoperability. That's what we did. That's what Seqster did. That's that's what we set out to do. And we did it. Some, you know, a lot of people say they can do it. Very few actually. Do we fit in that model now, right? And you had the experience yourself. And I think the first time I saw patient centric ads was. 2020. No, sorry. Yeah, 2020, JP Morgan Health Care Conference in January, just three months before the lockdowns and the pandemic started. It was the first time I went to Johnson & Johnson's afterparty in downtown San Francisco. And saw a huge banner saying, you know, blah blah blah, patient centricity. It's the 22nd century, you know, whatever. So they add a bunch of ads that were all patient centric, and I looked to my co-founder, Dana, and I'm like, Look at this, these guys finally caught on. I wonder if they've been, because we've been in discussions with a lot of these folks, long story short, it's not because of Seqster, I think it's just the market was headed that way. We were so far ahead of the market and there was no tailwinds. Now it is all there. And the pandemic afterwards accelerated digital health, as I say, by 7 to 10 years.[musical interlude]Harry Glorikian: Let's pause the conversation for a minute to talk about one small but important thing you can do, to help keep the podcast going. And that's to make it easier for other listeners discover the show by leaving a rating and a review on Apple Podcasts.All you have to do is open the Apple Podcasts app on your smartphone, search for The Harry Glorikian Show, and scroll down to the Ratings & Reviews section. Tap the stars to rate the show, and then tap the link that says Write a Review to leave your comments. It'll only take a minute, but you'll be doing us a huge favor.And one more thing. If you enjoy hearing from the kinds of innovators and entrepreneurs I talk to on the show, I know you'll like my new book, The Future You: How Artificial Intelligence Can Help You Get Healthier, Stress Less, and Live Longer.It's a friendly and accessible tour of all the ways today's information technologies are helping us diagnose diseases faster, treat them more precisely, and create personalized diet and exercise programs to prevent them in the first place.The book is out in print and ebook format from Amazon and Barnes & Noble. Just go to either site and search for The Future You by Harry Glorikian. Thanks. And now, back to the show.[musical interlude]Harry Glorikian: So the platform combines EHR, genetic, and fitness data, so. Why did you start with those three?Ardy Arianpour: So we started with those three, and I'll get to that, but we also do pharmacy, social determinants of health, and claims data as well. So we've added three other very large pillars. We can connect to any data source. We've created a universal interoperability platform that's patient centric that brings real time, real world data. And we're just super excited about all the business opportunities and the big pain points that we're solving for enterprise as well as for the patient. Why did we start with genomics, EMR, fitness. Ok. Here's the story. So I named the company Seqster after actually going on a five or six mile run in downtown San Diego, coming back and watching The Italian Job. And in the movie The Italian Job, it's one of my favorite movies, actually. I love that movie. I could just keep watching it over again, the real Napster was in the movie, and I used to be a Napster user where, you know, it was the way of actually pulling all your music and having it kind of in one place. Not really exactly Seqster's model, Seqster's model is is much more legal because it's patient centric. Yes, Napster was kind of stealing the data, right? So long story short, I was trying to think of a company name and I'm like, Oh my God. I don't know what hit me. I'll remember that moment like it was yesterday, Harry. Sequster came up because I had dived into DNA sequencing. We are doing everything that you can on next gen sequencing. And so I was like, Wow! Seqster. S-E-Q-S-T-E-R.Ardy Arianpour: And I went on GoDaddy.com. I bought it for $9.99. And the story started from right then. It was just me and the website. No co-founders, no onee else. I was just thinking, this is a great name. Now, you fast forward to why it's medical data plus genomic data, plus fitness data, to begin with. Well, the genomic data was an easy one because, right, I have 15 years underneath my belt on genomic sequencing technologies and clinical diagnostics and doing a lot of great things for patients in that arena. And I knew that it couldn't just be the genome, right? That's where the medical data came in because we knew and I never knew that we would be able to actually build something that would be able to pull it on together. I knew it was going to be really tough. I didn't think it was going to be this tough. We would have never done it if I knew that it was this tough. It's so great that we did because we solved it. But if you go back and say, "Ardy, would you do it again if you knew it was going to be this tough?" I wouldn't, because it's really, it's not the number two problem, it's the number one problem. And we're just, you know, I'm a peon. I'm a very small dot. I'm not anyone special. I'm just very passionate about solving this problem. That's it. And so is my team, and we got a great team and we've execute on. So great.Ardy Arianpour: And then, you know, it was my idea. I was forcing the wearable and fitness data because I was interested in that. And when the Apple Series One Watch came out, it was very limited, but I saw how it was going to change, you know, just connection of data. And my team being bioinformaticians and from the genomics world were so against bringing it in, I mean, I could show you emails of fights about me saying, get fitness data in here. They were not interested. I forced it on them. And then next thing you knew, clinical trials. One of the biggest things was how do you bring sleeping data and wearable data to x y z data? And that market started taking off. Decentralized trials. You can't even do it if you don't have wearable data. And so everyone started saying, you know, OK, you were right. That was one. I get one big pat on the back. And then we realized we can't be limited to just those three pillars. So what are the next three that we can work on? And that was claims data so we can marry it with the EMR and medical data for payers. And then we ran into pharmacy data. We just signed our first digital pharmacy deal three weeks ago with Paragon Health. And if we didn't have those capabilities, we wouldn't have the business opportunities. And the social determinants of health data being our last integrations comes in very handy for various different use cases.Harry Glorikian: So, three sort of things, right? You know, you combine all this data. What can you learn that wasn't obvious before? How do you translate into better health outcomes for consumers or, say, smarter decision making by consumers, right, so those are two potentially different ways to look at it.Ardy Arianpour: Absolutely. So one word for you: Seqster's longitudinal health record drives health economics, outcomes, research. It drives it.Harry Glorikian: Is that your clients doing that, you doing that, a third party group coming in?Ardy Arianpour: Yeah. We don't do that. We're just the patient engagement and data aggregation operating system that gets implemented for enterprise. And then the enterprise can run the analytics on top of it. They can, you know, take all of the raw data. So we're the only 21 CFR Part 11 compliant platform too. We're fully FDA compliant, Harry. It took us 19 months working with the FDA in order to get our compliance letter in September, October of last year, 2020. So about a year ago. And not only are we HIPAA compliance, not only are we High Trust certified and 256 bit encrypted on all the data that comes in, but having that FDA compliance sets us apart number one. Number two, because we're not an API, we have FHIR fully integrated. We have an API for sharing data, but we're not an API business. We're a SaaS business in health care, in digital health. We can make any company a digital health company. Let's say it's Coca-Cola, and they want to empower their 200,000 employees. They could launch a Coca-Cola Seqster white label in 72 hours to 200,000 employees. That's what we've created. Now, take that and imagine that now within pharma, within precision medicine, within clinical trials, within the payer network, which we're the only platform that's CMS ONC interoperability compliance from the Twenty First Century CURES Act as well.Harry Glorikian: So let me let me see if I... I'm trying to figure out like the angle, right? So I mean, ideally for interoperability, if we talk about the highest level right, you really want to get Epic, Cerner, Kaiser, et cetera, all in a room right? And get them to agree to something. Which is like an act of God.Ardy Arianpour: Some people say, we're doing, you know, it's not my words, but again, a figure of speech, people say, we're doing God's work.Harry Glorikian: But stepping back here for a second, what I see you guys doing is actually giving a platform to the patient and the patient is then connecting the record, not necessarily the systems themselves allowing for interoperability to take place.Ardy Arianpour: So yes, but you're speaking of it because of the direct to consumer experience that you had. The experience we gave you is much different than the experience from the enterprise side. We have a full BI platform built for enterprise as well. Right. And then we have the white label for the enterprise where they launch it to a million patients.Harry Glorikian: That's what, I'm trying to think about that, right? So. Coca-cola says, like, going down your example, Coca-Cola says, "Love to do this. Want to offer it to all of our employees." We make it available to them. But it's the employee that has to push the start button and say, yes, I want my electronic medical record to be integrated into this single platform, right?Ardy Arianpour: But that's that's an example with Coca-Cola. If we're doing something with Big Pharma, they're running a clinical trial for 500,000 COVID patients, as an example. They're getting data collection within one day versus two months, and guess what, we're going to be driving a new possible vaccine. Why? Because of the time it takes for data collection at scale. We empower patients to do that and they get something back. They get to track and monitor all their family health.Harry Glorikian: Right. So so it's sort of, you know, maybe I'm being dense, but sort of the same thing, right? Big Pharma makes it available to the patient. The patient then clicks, Yes, I want to do this and pull in my medical records to make it all everything to be in one place. Yes.Ardy Arianpour: Yes. And I think it's about the fact that we've created a unique data sharing environments. So that's, you know, Harry and Stacey and John and Jennifer and whoever, you know, with whatever use case can share their data and also consent is built with E-consent and digital consent is built within that process. You don't share anything you don't want to share.Harry Glorikian: Right. So let me see if I got this correct. So Seqster is providing a translation and aggregation between systems through a new layer of technology. Not creating true interoperability between systems, right?Ardy Arianpour: Yes. There's a spider web. And. We have untangled the spider beb in the United States of America. We've done all the plumbing and piping to every single health institution, doctor's office clinic, wearable sensor, medical device pharmacy, the list goes on and on, Harry.Harry Glorikian: So let's... Another question. So how does the 21st Century CURES Act of 2016 relate to your business? I think you know you've said something like Seqster has become law, but I'm trying to. I'm trying to understand, what do you mean when you say that?Ardy Arianpour: So when we founded Seqster, we didn't know there was going to be a Twenty First Century CURES Act. We didn't know there was going to be GDPR. We are GDPR compliance before GDPR even came out. Right? Because of our the way that we've structured our business, number one. Number two, how we built the platform by patients for CMS ONC interoperability, you know, final rulings and the Twenty First Century CURES Act, which is, they're synonymous. We worked hand in hand with Don Rucker's team and Seema Verma on the last administration that was doing a lot of the work. Now a wonderful gentleman, Mickey Tripathy has taken the role of ONC, and he understands, you know, the value of Seqster's technology at scale because of his background in interoperability. But what was interesting in the two years that we worked with HHS and CMS was the fact that they used Seqster as the model to build the rules. I was personally part of that, my team was personally part of that, you know, and so we were in private meetings with these folks showing our platform and they were trying to draft certain rules.Ardy Arianpour: We didn't know that they were going to be coming out with rules until they did. And then that's when high level folks in the government told us specifically on calls and also even at Datapalooza when I gave a keynote talk on on Seqster, when Don Rucker did as well right before me. You know, we're sitting in the speaker room and folks are like, "You're going to become law in a month." And this was in February of 2020. March 9th, those rules dropped. I was supposed to give a keynote talk at HL7,  at HIMMS. HIMMS got cancelled in 2020. I just got back from HIMMS 2021 in Vegas just a week and a half ago. It was fantastic. Everyone was masked up. There was only three cases of COVID with 10,000 people there. They did a great job, you know, regulating it. You had to show your vaccine card and all that good stuff. But you know, I would have never thought Seqster becomes law when we were founding the company. And so this is really special now.Harry Glorikian: So what does success look like for Seqster?Ardy Arianpour: It depends how you measure it. So we're in the Olympics. It's a great question. Here's my answer to you. We're in the Olympics just finished, right? So we started out in track and field. We were really good at running the 400 Meters and then somehow we got a use case on the 4x1 and the 4x4. And then we did really well there, too. And then because of our speed, you know, we got some strength and then they wanted us to get into the shot put and the javelin throw and then we started winning there, too. And then somehow, now people are calling us saying, "Are you interested in trying to swim?" We got the 100 meter butterfly. Well, we've never done that. So success for us is based off of use cases. And every use case that we deal with, within clinical trials and pharma, we've define 24 distinct use cases that we're generating business on. Within the payer community now, because of the CMS ONC Twenty First Century Cures Act, there's a major tailwind. Within life insurance for real time underwriting, there's, you know, a plethora of folks that are calling us for our system because of the patient engagement. So this patient centricity for us has been a central pillar, and I've never allowed anyone in our company, whether it's the board or our investors or employees, you know, get sidetracked from that. We've been laser focused on the patients and success at impacting patient lives at scale.Harry Glorikian: So as a venture guide, though, right, like I'm going to, there's only so much money on so much time to tackle, so many different opportunities, right? So it's there is a how do we create a recurring revenue stream and keep plugging along and then generate either enough revenue or raise enough money to do more? And so just trying to think through that for what you guys are trying to do, I get the 4x100 and the swimming. But all of that takes money and resources right to be able to prove out, of course.Ardy Arianpour: And here's another thing we're in a different state. Look, my team and I had a major exit before. We built a billion dollar company out of $3 million. And even though we weren't founders of that company, you know, I was the senior vice president and we we did really well. So, you know, that allowed us to not take salaries that allowed us to take our money and put it into doing something good. And we did that in 2016 to seed it. And then afterwards, I raised, you know, millions of dollars from folks that were interested in, you know, this problem and saw that our team had a track record. And I actually was not interested, Harry, in raising a Series A because of our experience, but we kept on getting calls. And then just six months ago, we announced, you know, our series a funding. Well, we actually announced it in March, I think it was, but we closed our Series A in January of this year and it was led by Takeda Pharma, Anne Wojcicki's 23andMe and United Healthcare Group's Equian folks that created Omniclaim and sold to UnitedHealth Group Omni Health Holdings.Ardy Arianpour: So check this out. Imagine my vision in 2016 of having medical data, genomic data fitness data. Well, if you look at the investors that backed us, it's pretty interesting. What I reflect on is I didn't plan that either. We got amazing genomic investors. I mean, it doesn't get better than getting Anne Wojcicki and 23andMe. Amazing female entrepreneur and, you know, just the just the force. Secondly, Takeda Pharma, a top 10 pharma company. How many digital health startups do you know within Series A that got a top 10 pharma? And then also getting some payer investors from UnitedHealth Group's Omniclaim folks and Equian OmniHealth Holdings. So this is to me, very interesting. But going to focus our focus has been pharma and clinical trials. And so Takeda has been phenomenal for us because of, you know, they they built out the platform and they built it out better for us and they knew exactly what to do with things that we didn't know. And with things that patients didn't know on the enterprise, you know, Takeda did a phenomenal job. And now other pharma companies are utilizing our platform, not just Takeda.Harry Glorikian: Yeah, well, they want their data aggregation. They want as much data on the patient aggregated in one place to make sense of it.Ardy Arianpour: So not necessarily that they actually want to empower patients with a patient centric engagement tool. That's pharma's number one thing right now, the data part, obviously is important, but empowering patient lives at scale is the key, and that's that's our mission. And so, yeah, that's that's a whole 'nother cocktail conversation when I see you soon hopefully in a couple of weeks.Harry Glorikian: Hopefully as life gets, or if it gets back to normal, depending on the variants, you know, we'll hopefully get to meet him in person and have a glass of wine or a cocktail together. So it was great to speak to you. Glad we had this time, and I look forward to, you know, hearing updates on the company and, you know, continually seeing the progress going forward.Ardy Arianpour: Thanks so much, Harry, for having me. Big fan of Moneyball, so thank you to you and your organizers for having me and Seqster on. If anyone wants to get in touch with me personally, you can find me on LinkedIn or you can follow Seqster at @Seqster. And again, thank you so much for. For having a great discussion around, you know, the the insights behind Seqster.Harry Glorikian: Excellent. Thank you.Harry Glorikian: That's it for this week's episode.  You can find past episodes of The Harry Glorikian Show and MoneyBall Medicine at my website, glorikian.com, under the tab Podcasts.Don't forget to go to Apple Podcasts to leave a rating and review for the show. You can find me on Twitter at hglorikian. And we always love it when listeners post about the show there, or on other social media. Thanks for listening, stay healthy, and be sure to tune in two weeks from now for our next interview. 

Мы уже не раз обсуждали что обязательно нужно знать о разработке под Android. Какие фичи Android SDK важные, что есть из крутых библиотек и фреймворков. В этот же раз мы решили затронуть тему вспомогательных знаний, которые не связаны напрямую с Android разработкой, но их наличие сильно поможет вашему и техническом, и карьерному росту.02:53 - Git.11:00 - CI.13:45 - Proxy, ReverseProxy, Nginx.19:25 - Local proxy. Charles, Fiddler.23:27 - IDE.31:32 - Command Line.40:02 - Знать особенности ОС, на которой работаете вы.43:36 - Знать как устроен ваш backend.46:05 - Обладать чувством прекрасного.Комментарии и пожелания можно оставлять в нашем телеграмм чате.

https://github.com/vector-im/element-android/

Когда-то давно, когда деревья были большими, а в Mobile People Talks еще не приглашали гостей, - ведущие уже поднимали тему Jetpack Compose. Пришло время вернуться к ней, так как гостем этого эпизода стал Матвей Мальков из имеющего самое непосредственное к этой теме места - компании Google. И мы точно можем сказать, что он каждый день видит этот тулкит изнутри, так как вместе с командой его и разрабатывает. Выпуск начинается под вой сирен лондонской полиции, ведущие даже в какой то момент начинают волноваться, что происходит что-то серьезное и в дверь к Матвею скоро начнут врываться суровые полисмены, а выпуск останется незаписанным. (СПОЙЛЕР) Все обходится благополучно, и ничто не прерывает запись этого эпизода. Что произошло с Compose за последний год? Насколько он готов к использованию в продакшене? Зачем нужен плагин к Kotlin компилятору? Использует ли Compose нативные компоненты Android SDK или рисует их на канвасе, как Flutter? И наконец, какие вообще есть отличия в подходах к декларативному UI у Jetpack Compose, SwiftUI, ReactNative и Flutter? Ответы на все эти, и многие другие ХОРОШИЕ вопросы, из первых рук, не пропустите) Наш гость: Матвей Малков, твиттер - https://twitter.com/matvei_jj Полезные ссылки: Jetpack Compose: https://developer.android.com/jetpack/compose Declarative UI patterns c Google I/O: https://www.youtube.com/watch?v=VsStyq4Lzxo Доклад Лиланда про внутренности компоуза: http://intelligiblebabble.com/compose-from-first-principles/ Видео с ADS: https://www.youtube.com/watch?v=Q9MtlmmN4Q0 Kotlin slack: http://slack.kotlinlang.org/ Пишите нам: mobilepeopletalks@gmail.com

F-Droid is an installable catalog of FOSS (Free and Open Source Software) applications for the Android platform. F-Droid is also a whole FOSS "app store kit", providing all the tools needed to set up and run an app store. It also includes complete build and release tools for managing the process of turning app source code into published builds. Hosts: Jonathan Bennett and Simon Phipps Guest: Hans-Christoph Steiner Download or subscribe to this show at https://twit.tv/shows/floss-weekly Here's what's coming up for FLOSS in the future. Think your open source project should be on FLOSS Weekly? Email Randal at merlyn@stonehenge.com Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: barracuda.com/floss twit.cachefly.com

F-Droid is an installable catalog of FOSS (Free and Open Source Software) applications for the Android platform. F-Droid is also a whole FOSS "app store kit", providing all the tools needed to set up and run an app store. It also includes complete build and release tools for managing the process of turning app source code into published builds. Hosts: Jonathan Bennett and Simon Phipps Guest: Hans-Christoph Steiner Download or subscribe to this show at https://twit.tv/shows/floss-weekly Here's what's coming up for FLOSS in the future. Think your open source project should be on FLOSS Weekly? Email Randal at merlyn@stonehenge.com Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: barracuda.com/floss twit.cachefly.com

F-Droid is an installable catalog of FOSS (Free and Open Source Software) applications for the Android platform. F-Droid is also a whole FOSS "app store kit", providing all the tools needed to set up and run an app store. It also includes complete build and release tools for managing the process of turning app source code into published builds. Hosts: Jonathan Bennett and Simon Phipps Guest: Hans-Christoph Steiner Download or subscribe to this show at https://twit.tv/shows/floss-weekly Here's what's coming up for FLOSS in the future. Think your open source project should be on FLOSS Weekly? Email Randal at merlyn@stonehenge.com Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: barracuda.com/floss twit.cachefly.com

F-Droid is an installable catalog of FOSS (Free and Open Source Software) applications for the Android platform. F-Droid is also a whole FOSS "app store kit", providing all the tools needed to set up and run an app store. It also includes complete build and release tools for managing the process of turning app source code into published builds. Hosts: Jonathan Bennett and Simon Phipps Guest: Hans-Christoph Steiner Download or subscribe to this show at https://twit.tv/shows/floss-weekly Here's what's coming up for FLOSS in the future. Think your open source project should be on FLOSS Weekly? Email Randal at merlyn@stonehenge.com Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: barracuda.com/floss twit.cachefly.com

Нет в Android мире разработчика, который бы не сталкивался с Gradle, и особенно с тем что она имеет свойство выполняться долго. Как ускорить сборку проекта? Какую "магию" применяют в больших проектах, где количество строк исчисляется не одной сотней тысяч? Помогают ли в этом рекомендации Gradle? Может пора переходить на Bazel? Обо всем этом мы поговорили с гостем - Степаном Гончаровым (https://twitter.com/stepango). Степан занимается мобильной разработкой более 10 лет. В настоящий момент Engineering Manager в Grab. Занимается CI/CD тулингом, билд таймом и продуктивностью 200+ мобильных разработчиков. Bazel фанбой. Организатор Kotlin User Group Singapore. Полезные ссылки: - Советы по улучшению производительность от команды Gradle https://guides.gradle.org/performance - Доклад Степана "Gradle pipeline optimization: Beyond basics" https://youtu.be/ez3mQoMZUBY - Kapt и разные опции https://kotlinlang.org/docs/reference/kapt.html - Официальный сайт Bazel https://bazel.build - Пример настройки Bazel и Android https://github.com/stepango/bazel-android-intro - Подключение Android SDK в Java модуль https://github.com/stepango/android-jar - Подключение AAR в Java модуль https://github.com/stepango/aar2jar Спасибо Александру Марцинкевичу за помощь в подготовке выпуска

In this internal Frontside Podcast episode, Charles, Taras, and Jeffrey analyze the NativeScript Mobile Platform. Please join us in these conversations! If you or someone you know would be a perfect guest, please get in touch with us at contact@frontside.io. Our goal is to get people thinking on the platform level which includes tooling, internalization, state management, routing, upgrade, and the data layer. This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC. Transcript: CHARLES: Hello and welcome to The Frontside Podcast, a place where we talk about user interfaces and everything that you need to know to build them right. My name is Charles, a developer here at Frontside. With me today are Taras and Jeffrey. TARAS: Hello everyone. CHARLES: Today, we're going to be talking about NativeScript, in particular, and evaluating technologies and frameworks, kind of at the meta level. So, I'm kind of excited about it because we've been pretty heavily involved with NativeScript for the past three months or so. And so, we've gotten to look at it both from beginners' eyes being kind of totally fresh to the platform, but then actually having to start to pump up against some of the edge cases which is what always ends up happening when you actually use a framework for real. Let's get started. TARAS: All right. I think there's a lot of things that we could talk about because when we would start looking at NativeScript, the length that we were looking at NativeScript through this is that this platform that our client is going to be using for doing development of large applications. So, what does NativeScript need to have to be able to support potentially hundreds of developers building apps? We started looking at it and one things that made us consider NativeScript early on was it kind of provides a platform that allows you to encode in JavaScript and run it on mobile. And we saw this kind of emergence of Angular and Vue.js running on top of NativeScript. So, those things together is kind of exciting. CHARLES: There was also an implementation in progress of React and there were a couple of spikes of Ember also running on top of NativeScript. So, my first impression was initially very favorable. The onboarding experience is actually pretty nice because it was JavaScript and the application was interpreted, there's the ability to completely and totally dynamically change the application at runtime. So, they have essentially an application called the NativeScript Playground which lets you flash a QR code at it and then it will go in to the URL associated with that QR code and it will download all of the assets for a NativeScript application running at that URL. So, all the JavaScript, all the templates, all the whatever, it'll pull it down, it will actually start running like within that app. So, the Playground app then becomes your actual app that you want to use. There's no App Store, no TestFlight, no Google Play. There's no gatekeeping to delivering your application into a running app. And I thought that was really, really cool and really, really compelling. TARAS: We should clarify that this is specifically for preview purposes because if you're going to be shipping the application to production, you still need to go through all those things before... CHARLES: Yes. TARAS: But the onboarding process, you could just install the preview app and then you can point a QR code and it will open that app, whether it's in Angular or in Vue, that app will open up in the preview app and you have a native app that you could play around with. CHARLES: Right. JEFFREY: And that's key both for the engineers who are playing around with this and building this and also really key for the non-engineers who are part of the team to be able to really easily spin up and see what the engineers on the team are working on. CHARLES: That's exactly why we thought, "Hey, we want to be able to use this mechanism for preview apps." In the same way on the server side, you have preview apps associated with a pull request. When we saw this, what we immediately wanted to do was have a bot post a comment onto a pull request with a QR code, so that anybody could just, boom, test out this app on their phone. TARAS: We ultimately ended up setting that up but not quite that way because the original idea of being able to have something like danger bot post the QR code to the comments, you can kind of point out with your phone and open the preview app, that didn't actually pan out. Charles tried to implement that. What happened there? CHARLES: What it actually turned out was that the preview functionality was dependent on a central server, a central NativeScript server. So rather than kind of statically bundling the assets and just saying 'these assets are this URL and just pull them in and bootstrap your NativeScript application that way', it required a lot of extra stuff. So, it required you to be running a Webpack Dev Server that was building your assets and then basically registering and doing some port forwarding with that dev server to a central NativeScript service that was provided by the company that underpins NativeScript. And that connection needed to be hot and live the whole time for that to work. So, while it was really cool that you could get the QR codes up and running, unfortunately that functionality could not be decoupled from the hot update and the central service. Those central services were kind of hard coded into the tools. TARAS: Yeah. So we eventually ended up implementing the preview apps that we wanted but we ended up using Appetize.io to essentially -- the process there is you build the app, you upload the app to Appetize and then danger bot embeds a link to a URL where you can open that app and it will essentially stream like it's running somewhere in a simulator for iOS, an emulator for Android and it will stream a video of that and you can interact with it, kind of like a VNC setup. CHARLES: Yeah. TARAS: And that actually accomplished the goal. It's just we weren't able to do the way that we thought we were hoping to do it straight off with the preview app mechanism. CHARLES: It accomplished the goal. And Appetize is an incredible service that lets you preview the apps on pretty much any type of Android device, any type of iOS device, right there inside of a pull request. But what it didn't allow us to do was pop up your actual device, your actual phone and scan a QR code off of the pull request and pull down the assets. That would have been amazing. But it doesn't always work out that way. And I don't know if that would work long term anyhow because you can't pull down native libraries over the wire and funk them in. That's a big, big no-no. So, the process does have limitations. But nevertheless, that part was really cool. TARAS: Yeah. That was kind of the entry point, the onboarding. And then I think one of the things that was kind of, I remember at the time when we were talking about the NativeScript architecture because we were starting to understand more about how it works. The idea itself is really kind of amazing actually because you have this V8 where you can run your JavaScript code and then they're kind of wired together on iOS and Android. They're wired to the native implementation. So when you're interacting with it, I think the thing that's really great about NativeScript is that the runtime environment for JavaScript essentially gives you API access. In JavaScript, you could say, "I want to create a Java view," and there will be a Java view that's rendered in the actual native device. You're using the same -- the APIs that you find on the Android docs or iOS docs, all of those APIs are available to you as JavaScript. So, you [crosstalk] as JavaScript. And it's seamless, right? CHARLES: Yeah, and it makes it very, very handy. The language is different but the APIs are exactly the same. There is an attempt to make cross-platform components and cross-platform classes that serve the needs on both platforms and then delegate to the platform on which you happen to be running. But those are not mandatory, and the low level APIs are always available to you. An example of this is in iOS, kind of the core foundational object is NSObject. All the controllers, the views, the things, all of them are descended from this object. I can go from object and I can go in from JavaScript and I can just say {let object = new NSObject} and boom! I've got a reference to the actual object and I can pass it around to any other iOS API. That is really, really powerful that there's nothing off limits. There's nothing at an arm's distance. There's really not much you can't do because all of those things are available to you. There's nothing that's off limits. That means that they can build cross-platform components on top of those APIs. Whereas a sort of system like React Native which does have cross-platform components, that's kind of where the base layer is but you can't crack open the hatch and go down the next level and start mucking around, unless you want to actually start meddling with the React Native source code or recompiling Swift in Java code. TARAS: For me, I think this architecture is probably my favorite part of NativeScript. JEFFREY: Mine too. CHARLES: Yeah, me too. TARAS: I really like this part. I kind of hope that everything else is as clever as that was. CHARLES: Because among other things, it allowed us to write a Bluetooth. We were able to implement Bluetooth using nothing but JavaScript. We didn't actually have to go down and do any Swift and do any asynchronous message passing between the iOS libraries and the JavaScript libraries. It's like, "No." We've just got a very simple cross-platform interface that instantiates an implementation for Android and an implementation for iOS, but both of them are like JavaScript. And so, it really is you're doing native development but it's JavaScript all the way down. TARAS: Yeah. And when you're writing plugins, your plugin is actually JavaScript plugin that is assuming iOS APIs and Android APIs. CHARLES: Yeah. And if you have to have a native plugin like a CocoaPod or an Android Package, you just install it and you can instantiate it from JavaScript. There's no fuss, no muss, no ceremony. It's just like, "Hey, I want to use the..." what was the one we like to use? The Material-UI floating button which is a CocoaPod. You download it, you link it into your application, and then you just instantiate it from JavaScript. TARAS: That was really cool. The challenging part was that a lot of that kind of awesomeness, like everything around it wasn't quite as polished. And so, one of the big things is that like around tooling, because one of the things about having grown up in a way like in the Ember community, in a sense, we have a certain expectation of what the level of polish from tooling that we would expect. And it's kind of supported in the way like when you look at how React or React Native tooling is, even Angular tooling, it's very polished. You kind of expect to see what you need to see when you're looking at a CLI input and you don't see anything else. That level of polish. I think part of the changes that they're going through, maybe that's part of the reason but that same level of polish isn't available around the tooling. CHARLES: There are these fantastic qualities about the platform and it is amazing. We were using Angular and a lot of people are using Vue and things like that and that actually is pretty incredible. And there is nice tooling, there is command line stuff, but we started to run into issues where, for example, it was very clear that we were pretty much, as far as I could tell, one of the very, very few people running a NativeScript project on CircleCI or in a CI environment at all. It had capability for testing, both for acceptance testing and for unit testing, but it required changes to the core framework and the core tools in order to get those tests to work in a CI environment. JEFFREY: Before we kind of get into the testing story there, some of the issues were around determinism of reliably reproducing your whole NativeScript environment and stack every time because that's such a key feature of doing it. And on a CI server, it's like, "Hey, we need this to load in the same exact packages every time." And so, we ran into challenges there. TARAS: I think we spent almost two days. There's example projects in different combinations. One thing that was off was that there's a pattern that is applied in a lot of the plugins in NativeScript ecosystem is installing things. So, you run npm install and npm install will generate some files. And so, when we're trying to move it over to a CI, there were files, like there's hooks, like TypeScript hooks that were excluded that you can ignore, but they were necessary to compile the TypeScript. And so, what was happening is when we're running these at CI, the application, we would build the app but the app would crash the moment that you start it. And the reason for that was that the JavaScript files that were transpiled from TypeScript to JavaScript, those JavaScript files were actually never included because they were never transpiled in CI because the hooks directory, like we weren't preserving it between our tasks and so... CHARLES: Right. We weren't caching. This was an artifact of the install. And so, we were caching the install, so essentially the yarn.lock was not changing. But the directory was not getting generated unless the cache key changed. TARAS: And we spent spent quite a lot of time... CHARLES: Two or three days out. TARAS: Yeah. CHARLES: What that said is, "Oh, nobody's really running this in CI." Nobody's actually building an app from scratch every time. TARAS: There are people in NativeScript team that actually does a great job of documenting. They did have example projects that exist but sometimes that example project doesn't fit like a perfect combination of what you're looking for. There was an example project that was showing how to run on CI but it didn't use TypeScript. And so, that's where we lost a lot of time. CHARLES: Right. JEFFREY: So, let's talk about testing since that's kind of the core, the most important part of why you even want continuous integration capabilities to begin with. What did we run into there? What did it look like? TARAS: Well, I think it's safe to say that we were really on a bleeding edge of testing capabilities in NativeScript ecosystem with Angular, at least. But I think it was still an interesting project. We were using the latest builds. And I have to say I think this is one of those things that's going to be kind of consistent through this, is like the people in NativeScript team are amazing. They're so easy to work with. They're so accommodating. When we ask for stuff, they're on it. But it was a lot of things we're trying to figure out like how do we run unit tests, what can we do. Ideally, we wanted to run, first and foremost, we started with how do we run functional testing. So we spent quite a lot of time trying to get Appium set up. I spent a good two to three weeks on that and it was not productively spent time. CHARLES: I think ultimately, we had to pull back from it. And there were a number of reasons. Part of that is there are multiple paradigms for how you can build your NativeScript application. So as we speak, there's a move towards using Webpack to build all of your JavaScript in your style sheet assets because it's very much like a React Native application. You've got style sheets, you've got JavaScript assets, that some of them might be in TypeScript, some of them you might be using Babel, and you need to actually transpile them down to include them in a way that your underlying JavaScript runtime is going to be able to understand. But that wasn't always so. They have their own build system and packaging system, they kind of used the TypeScript compiler ad-hoc, if you were using TypeScript, which we were. And so, this was kind of this orthogonal complexity, I guess, where you have your unit testing and it has to play nice with this one package or Webpack. There were multiple ways to package your app. And so, we ran into problems where, like TypeScript kept coming up as a problem and the way in which we were bundling our assets. So, in order to get TypeScript to work, we kind of had to get Webpack running. But the problem is it felt like three quarters of the tooling wasn't Webpack compatible yet. And so, it meant that other pieces of the build were breaking because of this. And so, we had to be on the bleeding edge of several different aspects of the runtime. And the problem is when you're on the bleeding edge, that can break other stuff. TARAS: But there's complexity in running on native platforms that I think a lot of this complexity is kind of leaking to development experience because one of the challenges is your tests need to run on the native device in the application. So, you have to build the app. You have to push the app into the actual device. So, there's like all the setup of installing the at the app on the device. CHARLES: You have to launch the simulator. TARAS: Yeah, right. CHARLES: To make sure the device is connected. TARAS: And you run your tests in there. So, that created kind of this situation where we say let's just kind of set Appium aside and just use unit testing which is a very small fraction of the kind of testing that we actually want to do. It will test very little. But let's just do that because getting functional testing to work was really kind of not going anywhere. So once we start doing unit testing, one of the challenges is that it takes like 30 seconds to start your tests. And then, if you for whatever reason, made a mistake, the moment you cancel the build, it leaves, like it doesn't clean up of itself well. So, it leaves processes running in the background. And so now, you spend another like 10 to 15 minutes Googling around for a cookie, "How do you find these processes and stop them?" So, we eventually settled on having a script that does that, but this is the kind of things you have to end up doing because there's a bunch of things that are wired together, but they're not wired together in a way that is seamless. And so, you end up kind of just debugging a lot of stuff where you just want to run some tests but you end up doing all these other stuff. CHARLES: Right. TARAS: And you spend a couple of minutes just doing something that you'd expect to happen in like 20 seconds. CHARLES: Right. There is a feeling that every aspect of the system is coupled to every other aspect of the system in kind of varying ways of interconnectedness. And that's not what you want for a very, very complex system. You want it to be extremely modular. So, I think we should keep the command line tool. There's probably a separate discussion, I think, about that. But you have to close the book on the Appium and the unit testing. I think the other problem was that you have to run these things on simulators. On macOS, that's not a problem because the simulators ship with X code. And so, you don't actually require an external service. Whereas in CI on Android, it's very unlikely that you're going to have Android emulators on hand because they require a separate virtual machine. Android emulation is actually quite heavy. If you're running through Android Studio or something locally, you essentially need VirtualBox or some equivalent to run your Android simulator because you actually need that simulated hardware. If I understand correctly, that was actually not something that had been really accounted for. It was that you might want to be running simulators not on the same machine as what you were developing on or what the actual that you were building on. TARAS: Yeah, a lot of the tooling seems to be designed around this idea that you're going to be building and running everything on your machine. And so, you can spin up a virtual machine easily. But in CircleCI, for example, they don't support running a virtual machine inside of a Docker container because for that, you need a feature of a virtualization that is not supported in many CI platforms. You have to run a parallel server if you want to have like Appium running, for example. You need to have a separate server running like an Azure or a Google Cloud somewhere that is able to run virtualized servers that have a host machine that's being guest systems that are running the actual Android emulators of different versions. And so, when I started doing research in this, there are companies that are doing this really well but it's not unusual to be using hardware from Amazon that costs thousands and thousands of dollars per month. I think for anyone who's getting into mobile development, I would say the hidden gem of Android world is Genymotion. Those that do a lot of Android development, they know about it. But Genymotion has both like a desktop environment and it has SaaS offering that they're in the process of releasing. And so, what it allows you to do is when you run it locally or on your local machine, it allows you to create a virtual machine that is running in VirtualBox and then it allows you to run kind of optimized environment for running Android. And when you do that, it's really fast. It's very smooth. It makes running Android devices locally as easy as it is to run iOS devices on macOS. CHARLES: I remember starting out and trying to actually just get any Android emulator running on my Mac and I couldn't even do it. JEFFREY: It was such a huge time saver. CHARLES: Yeah. TARAS: And to have this Saas offering is really great because you could basically create your virtual machines on demand and then you install into a virtual machine from your CI server and then you run your tests there. That's kind of the key that I found to be able to run tests and automate it against emulated devices for Android. Genymotion is really great. CHARLES: Yeah. Again that's the kind of thing that you need when you're in CI. And so, one of the things, I think, one of our discoveries is that there just isn't -- when we started working on this and we haven't seen a culture of running these tools in the cloud and accounting for the fact that you might have not all of the tools running on the same machine. From, I would say, the beginning, I remember the kind of the diagnostics command didn't work but we were running it on a CI server. So, there's a diagnostics command that you run to see do you have this, do you have that, do you have that. It would work and give meaningful results when I wanted to debug my CI server because when we were initially getting set up, something wasn't building right, there was some dependency missing. And I just wanted a diagnosis but it was trying to install all those tools for me. And I was like, "No, no, no. I don't want you to do anything. I don't want to install them. I'm going to be doing all of that as part of the setup of the CI environment. It's going to be installed, it's going to be cached. I don't want you to just try and like massage my system into a suitable state for NativeScript development. I just want you to diagnose what is wrong. Tell me, am I missing this compiler? Maybe I've got the wrong version of Android SDK. Tell me what's going on." And I couldn't get that to work. That was very frustrating. I think it was because the kind of bulk of the assumptions was that it was going to be individual developers working on their own laptops or their own desktop computers to build, to test, to distribute these applications. I think that's becoming less and less the case. I mean, at this point, that's not a way that we're willing to operate. TARAS: And we eventually figured out how to do all this stuff, right? CHARLES: Yeah, we have. JEFFREY: We have. TARAS: We have the entire process working but it took a lot longer than one would imagine. It took all the time that we had allocated to it which we thought was very generous amount of time but it took like almost a month to get everything set up. The great part of this is that we do have now everything working. And so, there's a repo where people could take a look if they want to get all stuff working on CI, but it took quite a bit of work in figuring out. CHARLES: Yeah. Actually, I think worth probably a Screencast to show some of those capabilities because it is really exciting. I mean, when you actually think about the pipeline in its entirety. But we never were able to get functional testing working. TARAS: And then the challenge here is that because we were essentially looking at NativeScript, going back to this question like, "What do we need to be able to have like hundreds of developers potentially running on this platform?" And so there's a lot of considerations and this tool is just one of them. I think the other one that is a big one is like what are the capabilities of the view layer because that's where most of developers were spending most of their time. We got stuck a little bit about that because I spent a lot of time working in the view layer. The thing that was really great and the thing that I really liked about it is the fact that you have a collection of components that you can use in Angular. You render it as component and then that component is going to look correctly on iOS and is going to look correctly on Android. From a single code base, it's building appropriate components for iOS and Android. What I think is really confusing in that case, though, is because the Android and iOS components don't have parity in a sense. They don't behave exactly the same. And there is also a kind of a reputation in the NativeScript documentation that Android tends to be slower, much slower than iOS. And so, when you start to run into performance problems and you start to run into those pretty fast because it is not really clear what is necessary to not optimize NativeScript, when you start to run into performance problems, it's not really clear like where is it coming from. Right now, the profiling that they have for the UI is very limited. They're kind of in the process of migrating over to chrome.debugger, but profiling in chrome.debugger is not implemented. You can do performance optimization using Android tooling but that's only going to tell you performance of the Java side, or the iOS side is not going to tell you the performance of the code that's running inside of JavaScript. It's not really clear what is causing the problem. If you don't know what's happening, you kind of write it off as like, "I think it's just Android being slow." In reality, when you actually start to dig deeper, you realize there's things about the Android implementation of the components that are different or the views that are different than iOS. And it's the differences that add up to weird performance problems. That's probably the thing that gave me the most hesitation because one of the things that made me think like if we want to be able to give this to a team of like 50 people, we need to have our own view layer because we cannot rely on components. An example of this would be, they have a list ticker on iOS, it doesn't omit change events when you scroll. If the list is moving, it change events and not omit it. But on Android, every time that a different item shows up on a screen, it changes the selection. And so now, you've got this view that's a meeting on Android as a meeting change events. I made an issue around this and the response was that while there's a workaround that you can have for this, but that's hard. Work around is not a solution. CHARLES: Right. When you have a leaky abstraction like that. TARAS: Part of the problem is because people use leak abstraction. And so, what's happened in Native -- we actually got on the call with NativeScript core team and they're excellent in really being very helpful, understanding what the problems are, and providing pass on making things better. But what's happened as a result of having this leaky abstraction is that people are relying on the leak. And so now, the leak is the API. And so, we can't change that. JEFFREY: Right. CHARLES: And the answer that you really need there is, "We can't change that without breaking stuff. Here's our migration path for deprecating this and introducing a new API." And that gets more into the process stuff and it seems like the process for making changes to the underlying API, I think, could use a little love in the sense that it's kind of opaque as to where the platform is going. There's not a concept of like an [RSC], there's no roadmap about what to expect. What is this API going to look like in the future? Is this stable? If I were writing a software and someone said, "Hey, there's this leaky abstraction," I think my reaction would be, "We've got to fix this." And we also have to acknowledge that there are users who may depend on this. And so, we have to be very deliberate about it. TARAS: The challenge with this too is that NativeScript kind of outgrew its hands because I think originally, it wasn't meant to be hosting Angular and hosting Vue. Vue didn't exist. Angular didn't exist when NativeScript started. So I think what's happened is that these views that were available, I wouldn't call them components because they don't act like components, but they're exposed in Angular like components but the API feel like Vue objects. So these Vue objects that you consume, that you render in Angular, for example, or in Vue.js, they are the same APIs that NativeScript had before Angular and Vue.js. CHARLES: Right. You know what? It feels like there's a MVC framework, like a Circa 2010, 2012 MVC framework that has now become the foundational layer for Vue frameworks that have had significant advances in the way we conceive of model in Vue and how data is generated and passed around and how views are rendered off of the data and how reactivity is changed. But there's still, the underlying platform has not evolved. And in fact, this was originally user-facing APIs and now these APIs have become foundational for other user-facing APIs but haven't had the iteration and evolution to make them robust. TARAS: And flexible enough. As a result, you have the situation where not only is it really super easy to deoptimize the views simply because the requirements of keeping performance expectations are not obvious. One of the things that I found is that the list which is, lists are like 50% of most applications. Before I go into the problem with list, the nice thing about lists in NativeScript is that because they're interacting directly with native APIs, you have really fast list when they're optimized. They're really easy to work with. But they easily get deoptimized by the fact that the expectation to keep the list fast, you have to use this API in NativeScript called array observable and observable. And this is not to be confused with like... CHARLES: [Inaudible] observables? TARAS: Yeah. CHARLES: It's not to be confused, but in fact, every conversation involves a lot of confusion. Because we were using observables, right? TARAS: And we were actually using observables. So, we're using observable [inaudible] and we're using this array observables and object observables. And so, it's necessary for NativeScript to, essentially what it expects for list to be fast, is it expects that it's going to receive an array observable which is an object that wraps an array because it needs to know when an order or length of data rate changes. So what happens when you pass an array observable, a NativeScript array observable into a list? It will listen for change events on that object. But if you want to change the value of each of the items, like if you want to change a property on the object and have your view remain optimized, the array observable has to have an observable object which allows NativeScript ListView to listen for changes, property changes on the object. You pass this array observable which contains observables that ListView listens for changes on to make sure that it knows how to correctly apply this change to the list. If you don't have this magic, like if you haven't figured out this recipe for ListView performance success, you're going to have a really hard time because it's really not clear at what point and how this thing got deoptimized, why has it just gotten slower. CHARLES: There's a lot of iteration that needs to happen there and it's not clear what the plan, what the priority, or even how you will even begin to go about this. Because I think that the internal working is that it seems basically to be controlled by one company. I don't recall seeing any contribution from anybody except for Progress which is Progress Incorporated is the company that's kind of the controlling interest, the original company that developed it. TARAS: The way this showed itself very practically is that to make changes too -- so they have a ListView which comes with NativeScript public and there's RadListView which is the component that has a lot of stuff on it. Like if you want to pull to refresh or if you want to do like laser loading a data or if you want to do a filtering, you want to do -- so most people use RadListView. But RadListView, you can install, so there's no limitation when you build to install it, and your node modules has the source code for that. But the source code, the original TypeScript code, untranspiled code is not publicly available. They have a process for doing this and it's very nice that everybody's very kind and very accommodating. You send an email, they'll give you access to this repo and then you'll have the ability to contribute. NativeScript core team is very helpful and they're open to contributions. There are changes that need to be done to the Angular implementation to make it faster without having to put the requirements of the observable thing, and so they can give you a path to make that stuff happen but it's not open source in the sense that it's not a traditional open source that we would kind of expect. So, there's all kinds of hoops that you need to jump through and the source code is very difficult to read because it's transpiled from TypeScript to JavaScript. CHARLES: And there was a certain level of opacity in terms of process. For example, I filed an issue which was actually a blocker. For us, it was actually causing our Android build not to work. I didn't hear anything about it. And then, all of a sudden like four days later, a fix came through referencing another repository on which this thing depended with. There was not a lot of context service. So it was obviously referencing a bunch of context that probably happened between two people in a face-to-face conversation. But I couldn't really tell what was going on, why it was an issue, because there was no comment. It was just a pull request that was referencing this issue. I never got a notification. I actually had to go and be like, "Hey, I really would like for this issue to be solved. I wonder if I..." I was actually going to post a, "Hey, is there any progress on this?" Or, "Is there any way that I can help? What can I do to get this looked at?" And I saw that there was another pull request that had referenced my issue. And it was merged and I looked down, but then there was no indication of when this would be available for public release, how I might be able to work around it. And so, the strange loop that didn't get connected was, "Hey, you've got a user who files an issue. You actually use this as the impetus to fix the issue and make a release." But then that whole process was completely invisible to me. TARAS: You know what? It sounds like you wanted for it to work [inaudible] but you got a pulling mechanism. CHARLES: Yeah, exactly. Well, I wanted someone to say like, "Hey, here's what's going on, and we're looking right into it." Or, "We're going to look into it in like two months," or, "We can't address this now. But here's a workaround for it." Or, "I don't have a workaround." That's just kind of the expectation that you have when you're playing with open source. In many ways, it does not feel like an open source project. TARAS: Let's just do a quick note about Saas. Jeffrey, what did you find about the styling of NativeScript views? JEFFREY: All the components that come kind of shipped as part of the NativeScript core set of components all have styles attached to them. They have CSS attached to them. And as part of the standard data script workflow, with your build toy, you have SaaS available which is very nice. But actually on a recent project, we're not using Saas at all. We're simply using post-CSS and we were able to kick out some CSS variables that turned out to be really nice for theming. So as kind of a future friendly experiment, we were trying to have a light theme and a dark theme since that is very recently now a core part of Android and very likely will be part of iOS this year, where there's kind of a light theme and a dark theme for everything. We were trying to do that. The simplest way to do that with standard web tools is with CSS variables. You can have the flexibility, you have the theming with those. It's so nice. You just, "Hey, my primary color is this color in one scenario and it's this color in another." And we just didn't really have the flexibility to do that with SaaS by itself. And so, that's kind of a limitation of the tooling right now that I hope in the future, we'll have some more sophisticated CSS tools. And really, NativeScript's move toward Webpack and having that as a primary part of the workflow really opens up that possibility that I hope somebody runs with in the near future. TARAS: Yes, let's bring it all back together. CHARLES: Can we pause for a moment? Because I actually do think it's important that we at least touch on the command line. I can give a little bit of a kind rant in here but I think that's actually something really important that we have to talk specifically about that. The other thing that I wanted to touch on very briefly as we kind of draw to the close is the command line tooling, in particular in NativeScript. I think that this is probably one of the weakest points of the platform. And again, I don't want to disparage anybody working on NativeScript. It's an extraordinarily complex problem. This is a command line tool that needs to manage launching simulators, installing things into simulators, pushing code to those simulators. It needs to handle hot updates to things that it's running on, devices and simulators. So, it needs to be building JavaScript assets either with Babel or with TypeScript. It needs to be building those SaaS assets that you were just talking about, image assets. But it needs to be doing all of this for two platforms, so it needs to be managing everything that I just described. It needs to be managing on iOS. Everything that I've just described needs to be managed on Android, as well. It needs to work for a single developer's desktop. It also needs to work with all of those components that I just described distributed out in the Cloud. So, we're talking about an extraordinarily complex piece of software. And I think that unfortunately, the NativeScript CLI does not inspire confidence because it can do all of those tasks. But Taras, you also mentioned often if you stop the process midway, it will leave a thousand things open and they're just spewing output to your console. The console output, unfortunately, means there's a big noise to signal ratio because it puts out all of the content for Webpack. Every little thing that it's doing with any of the devices, it's logging to the console. So, it doesn't give you a sense of control. So, what you really are looking for in terms of a command line is, "Hey, I've got this incredible sprawl of complexity and I want to feel like I'm on top of it." And unfortunately, by leaving these things open and having so much console output and having the console output not be formatted well, there's all kinds of colors. Every single tool that you're using whether it's Webpack or whether it's Karma or whether it's just console outputs that you are happing inside of your NativeScript application, the brand of those tools comes through. Webpack is a great example. Its console output feels very Webpack. So when you've got Webpack content randomly interleaved with your console content from your Mocha content, from Karma, all of these competing brands, it doesn't feel like a cohesive developer experience. And so, I really, really hope that -- so, to the point being where I felt like I could not live with that command line tool without rewriting it myself. If we want to use this platform long term, we'd have to either have an alternative command line tool or really, really, really help the NativeScript team completely and totally rewrite the command line experience. TARAS: I would love to work on fixing a lot of these parts about NativeScript if there was a way to actually do it in terms of like, if they wanted to pay us to help them kind of bring some of these things to a state that would match. For example, what's available in Ember or available in React CLI, I would love to do that. CHARLES: React Native, yeah. TARAS: Yeah, let's do that work. But who knows what's in store? A lot of awesome platform like the idea around NativeScript architecture is fascinating and it's really, really powerful and really wonderful people doing some, trying to tackle really challenging problems, but it's all glued together in a way that doesn't instill confidence. And it just makes everything feel wobbly, just makes it feel like you never know, is it a problem? Where's the problem from? What is causing this? CHARLES: Yeah. And if I fix this thing, is it going to break something else? TARAS: Yeah, we've seen it happen actually with one of the solutions that was introduced to a bug that you were referring to earlier. CHARLES: Yeah. So that was our three months experience working with NativeScript. TARAS: We are considering other things now, very seriously looking at Flutter as an alternative for the same client, same scenario. Flutter is looking pretty exciting. There's a lot of things that are really good there. So in three months, we'll do another report and talk about Flutter and what we found. So, that's it. CHARLES: And I will say I'm actually not like super excited about dart but I'm in dart spot. JEFFREY: That's a whole other conversation for yet another episode. CHARLES: I think that, to continue the conversation maybe next week, next time we have kind of an internal podcast, is I would like to really talk about platform evaluation because really you need three months, at least, to get a good idea of this. Is this going to work for the next five years? And most of the time, we give it a week or give it a two week. Or someone comes on who's really excited about this one particular technology and you go off on that tangent. I think there's an interesting meta discussion about how do you select technologies. And we don't have time for that now, obviously. But it's definitely something that I want to have in the future. TARAS: Sounds good. I think that will be a good conversation for sure. CHARLES: I guess that is kind of the executive summary on NativeScript from our perspective. With us being three months in, I think, like you said, there's a lot there. Thank you for listening. If you or someone you know has something to say about building user interfaces that simply must be heard, please get in touch with us. We can be found on Twitter at @TheFrontside or over just plain old email at contact@frontside.io. Thanks and see you next time.

In this episode of the Xamarin Podcast, Pierce Boggan and James Montemagno discuss news from Build 2018 for mobile developers, including Xamarin.Forms 3.0, Hyper-V support for the Android emulator, Xamarin Essentials, and updates to Visual Studio 2017 and Visual Studio for Mac. 6:20 What's new in Visual Studio 2017 version 15.7 6:30 New XAML IntelliSense engine 9:55 Automatic iOS provisioning 13:00 Eager deployment for Android app development 14:15 Android SDK management 16:00 New Xamarin.iOS and Xamarin.Android project templates 17:10 Hyper-V support for the Android emulator 24:30 Xamarin.Essentials 33:30 Xamarin.Forms 3.0 All Things Xamarin at Build 2018 (https://blog.xamarin.com/xamarin-build-2018/) Visual Studio 2017 version 15.7 (https://blogs.msdn.microsoft.com/visualstudio/2018/05/07/visual-studio-2017-version-15-7-and-version-15-8-preview-1/) New Xamarin.Forms IntelliSense (https://blog.xamarin.com/new-xamarin-forms-xaml-intellisense-visual-studio-2017/) Automatic Provisioning in Visual Studio 2017 (https://blog.xamarin.com/automatic-provisioning-visual-studio-2017/) Eager Deployment (https://blog.xamarin.com/visual-studio-2017-version-15-7-preview-3/) New Xamarin.iOS and Xamarin.Android Project Templates (https://blog.xamarin.com/new-xamarin-android-ios-templates/) Hyper-V support for the Android emulator (https://blogs.msdn.microsoft.com/visualstudio/2018/05/08/hyper-v-android-emulator-support/) Xamarin Essentials Documentation (https://docs.microsoft.com/en-us/xamarin/essentials/) Xamarin.Forms 3.0 (https://blog.xamarin.com/xamarin-forms-3-0-released/) Visual State Manager (https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/visual-state-manager) FlexLayout (https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/layouts/flex-layout) CSS (https://docs.microsoft.com/xamarin/xamarin-forms/user-interface/styles/css) Right-to-left Localization (https://docs.microsoft.com/xamarin/xamarin-forms/app-fundamentals/localization/rtl) Follow Us: James: Twitter (https://twitter.com/jamesmontemagno), Blog (http://motzcod.es/), GitHub (http://github.com/jamesmontemagno), Merge Conflict Podcast (http://mergeconflict.fm) Pierce: Twitter (https://twitter.com/pierceboggan), GitHub (https://github.com/pierceboggan) Subscribe: iTunes (https://itunes.apple.com/us/podcast/xamarin-podcast/id691368176?mt=2) Google Play Music (https://play.google.com/music/listen?u=0#/ps/Ifcss44ww5lc375esulsuettsey) Overcast (https://overcast.fm/itunes691368176/xamarin-podcast)

In their Barcelona tradition, Jon Reed of diginomica and SAP Mentor and cloud expert Dick Hirsch review the news, debates, and questions from SAP TechEd Barcelona 2017. They break down what they learned on Leonardo, along with questions about how SAP got away from process expertise in their positioning. Separating hype from reality includes a review of SAP's blockchain pursuits, and why cloud requires a different level of pricing transparency. The guys also hit on SAP's multi-cloud ambitions, including the Google partnership, and Jon reveals what he learned - or didn't - on the Android SDK possibility in the future.

In their Barcelona tradition, Jon Reed of diginomica and SAP Mentor and cloud expert Dick Hirsch review the news, debates, and questions from SAP TechEd Barcelona 2017. They break down what they learned on Leonardo, along with questions about how SAP got away from process expertise in their positioning. Separating hype from reality includes a review of SAP's blockchain pursuits, and why cloud requires a different level of pricing transparency. Can SAP flip the pricing script? The guys also hit on SAP's multi-cloud ambitions, including the Google partnership, and Jon reveals what he learned - or didn't - on the Android SDK possibility in the future.  Yes, you can get Busting the Omnichannel on iTunes.

News The LinkedIn advertising hack that gained a company $100,000 funding for a penny! LinkedIn Announce their Q1 results. Financial analysts are OK with the results but hate the revised prediction for Q2 and shares plummet! Sponsored update advertising grows by 40% and the number page views grows at impressive rate again. LinkedIn hints that the Lynda.com acquisition will result in 'cross selling models and integration'. What exactly will this mean? So this is why LinkedIn bought all those copies of Reid Hoffman's new book Commentary LinkedIn published posts desperately need a 'read it later' feature. We all lead busy lives so the chances of having the time to read a long form post when we see it are limited. Perhaps a feature similar to Twitter's 'favorite' link would be the easiest option. At the moment I suspect we are kidding ourselves if we believe the 'read' numbers as people who have actually read the post. What do you think? Drop me a line at mark@linkedinformed.com. Question. This week's question comes from Carl, it's more of a point/commentary than a question but a really interesting one; Hiya Mark,I was just thinking about LI buying Lynda, and the imminent arrival ofFacebook at Work.If LI wanted to go mega they'd be tackling this by looking at systemslike Slack https://slack.com. This would really get them into companiesby becoming an actual part of the employees daily workflow, which iswhat I'm betting the FB at work thing will aim for. Right now, LI isstill broadly seen as the thing you use when changing jobs (rightly orwrongly).We all know how big mobile is now, and how it's just getting bigger eachday.Slack has massive take up and is really well respected. The need for LIto get a better collaboration tool will come soon anyway, 4G is here nowwith rich services growing daily.  We're about to be hit by the wave of"realtime videoisation" - all apps will be able to use it (its in thenext Android SDK) - think Twitters Periscope, which I know you love, butfor any app. And obviously phone/video calls. Right now, how can a LIuser call another LI user? Use their phone number. That's 3G and earlier- old style GSM. This next IP-only system allows username to usernamecalls within a closed system, such as LI, FB etc - and its much morethan a traditional phone call. ANS = I totally agree with this. LinkedIn challenge is to combine moving with the times and giving users a really valuable tool with protecting members from spam - unwanted messages and calls. To be honest though I suspect this is way beyond their capabilities at the moment. I have unofficially heard that they are already really struggling with mobile as it is so this seems a bit of a stretch for them! Perhaps this is inevitable outcome of rejecting partnerships with 3rd party developers? Opening up the API provides so much opportunity for innovation but LinkedIn are closing down their API and trying to do everything themselves.

Fresh from the keynote at Tech Ed Europe in Barcelona, Jeremy Thake talks to Carl and Richard about the latest announcements around Office 365. The development story in the cloud continues to evolve, and Jeremy talks about the Office 365 APIs going into general availability, along with an Android SDK. The iOS SDK is right behind it, currently in preview and ready for you to start building apps for iPhone and iPad that work with Office 365. The story is huge - new programming models for Exchange and Sharepoint in the cloud mean its easier than ever to create automation and make your company's Office experience even better!Support this podcast at — https://redcircle.com/net-rocks/donations

Fresh from the keynote at Tech Ed Europe in Barcelona, Jeremy Thake talks to Carl and Richard about the latest announcements around Office 365. The development story in the cloud continues to evolve, and Jeremy talks about the Office 365 APIs going into general availability, along with an Android SDK. The iOS SDK is right behind it, currently in preview and ready for you to start building apps for iPhone and iPad that work with Office 365. The story is huge - new programming models for Exchange and Sharepoint in the cloud mean its easier than ever to create automation and make your company's Office experience even better!Support this podcast at — https://redcircle.com/net-rocks/donations

Ich kann noch programmieren! Gestern Abend hab ich mir mal wieder ein Linux eingerichtet und das Android SDK installiert. Rausgekommen ist eine klein Android App, mit der ich meine wichtigsten Feedburner Statistiken abrufen kann: wieviele Abonnenten hat der Einschlafen Podcast? Falls Ihr auch Feedburner benutzt, könnt Ihr Euch beim Github Projekt den Source Code oder auch das Kompilat holen. Wie beim Einschlafen freue ich mich auch hier über Feedback.