#what is androidx

[birajtech]

Why you should consider ANDROID X migration?

Having trouble fixing your support library version? Not anymore! AndroidX is now available to resolve your issue.

What s AndroidX?

Along with Android Jetpack, an open-source project called AndroidX is presented.

In essence, it represents a significant upgrade over the original Android Support Library.

AndroidX, like the Support Library, ships independently of the Android OS and offers backward compatibility between different Android releases.

The older support libraries up to version 28 will continue to be made available in their current form, but newer versions of the libraries will be made available starting with version 1.0.0 of the AndroidX package overhaul.

Why you should migrate your app to Android X?

The life of the Android Support Library has ended. The Android Support namespace has not been updated since its final release, which was version 28.0. So, you must switch to Android X if you want bug patches or new features.

Other libraries, such as Google Play services, Firebase, Butterknife, Databinding Mockito, and SQL Delight, have switched to using the AndroidX namespace libraries.

The AndroidX namespace will be used for the release of all new Jetpack libraries. You must switch to the AndroidX namespace in outilize utilise features like Jetpack Compose or CameraX, for instance.

The Jetpack Navigation Component must adhere to Google’s recommendations. Simple Single-Activity Architecture App Approach.

Better package management: AndroidX offers independent, standardised versioning, better name standards, and more regular releases. Other libraries, such as Google Play services, Firebase, Butterknife, Databinding Mockito, and SQL Delight, have switched to using the AndroidX namespace libraries.

Migration is required: The AndroidX namespace will be used for the release of all new Jetpack libraries. You must switch to the AndroidX namespace in order to utilise features like Jetpack Compose or CameraX, for instance.

Simple App Architecture: Adopting Google’s suggested Single-Activity App Architecture requires the use of the Jetpack Navigation Component.

Google suggested using Arch Components and the MVVM paradigm with repos. To make the code base scalable, maintainable, and to get better CC, it is inevitable to create big-scale programmes using a modular architecture to isolate via modules.

CONCLUSION:

Upgrade to Android X effortlessly with BirajTech. If you’re seeking a seamless transition of your current Android app to Android X, BirajTech Services is your ideal choice. As a pioneering software company, we specialize in delivering top-tier mobile and web solutions for all your needs.

[globaljobalert-blog]

Senior Technical Writer - Remote

Company: Gradle Enterprise Gradle Enterprise is a first-of-its-kind product that software teams use to accelerate and optimize Gradle, Apache Maven™, Bazel, and sbt builds. It comprises several facets, including large-volume data ingestion and processing, complex data analysis and visualization, and distributed caching and execution systems.  Our software is used by some of the world's leading software organizations, such as Netflix, Airbnb, Spotify, SAP, several top ten banks, and many other major customers across all verticals. We regularly collaborate with these and other users to make our products continuously better. We have partnered with the Apache Software Foundation, the Micronaut Foundation, and other OSS projects like Spring, Quarkus, Kotlin Compiler, JUnit, AndroidX, etc., to bring the values of Gradle Enterprise also to the OSS Community. Profile We are looking for an experienced technical writer for Gradle Enterprise. The person in this role will improve our customers’ user experience by creating, extending, and restructuring our publicly available technical documentation, ultimately making our customers more knowledgeable and self-serving. The person in this role will work closely with the Gradle Enterprise Engineering and Developer Advocacy teams.  Responsibilities - Owning all user-facing Gradle Enterprise documentation, which includes creating new and maintaining existing documentation around installation and operations of Gradle Enterprise as well as documenting the functionality of Gradle Enterprise - Receiving product changes from Engineering and embedding them into the Gradle Enterprise documentation  - Coordinating, driving progress, ensuring consistency of all documentation, and being the first point of contact for anything related to documentation Minimum Qualifications - Experience writing technical documentation around enterprise SaaS products  - Experience deploying and using enterprise products  - Knowledge of AsciiDoc and/or Markdown - Knowledge of Linux systems and common commands - Knowledge of cloud platforms  - Knowledge of build and CI tools - Ability to plan and carry out large-scale documentation changes - Ability to initiate, implement, and maintain multiple projects concurrently - Excellent writing skills in English Preferred Qualifications - Software engineering experience - Knowledge of Kubernetes  - Familiarity with docs-as-code processes - Passion for writing and breaking down complex technical concepts into digestible content for a wide audience What We Offer - Work on a widely used product with a clear vision for the future - Contribute to leading solutions in the new industry of Developer Productivity Engineering - Close collaboration with experienced and dedicated engineers - Opportunities for growth in leadership responsibilities - In-person meetings, such as our annual company offsite and team meetings - Work from home in a remote-first environment  - Competitive salaries and equity grants Benefits & Perks - A focus on learning and development – Gradle offers an annual learning and development stipend and a monthly company-wide Learning Day, where we encourage all team members to focus on their professional development for the day - A hardware package that includes a laptop, monitor, other peripheral hardware, and a home office stipend to make sure you are fully set up to work remotely - Generous paid time off - Paid public holidays - Volunteer Day – We offer up to 8 hours of paid work time each year for team members to give back to their local communities Location - Anywhere in the world with working conditions that allow for seamless collaboration with your colleagues through email, chat, and video streaming - While our team works remotely and is spread across the globe, we deeply value daily interactions and collaboration. How to apply Please answer the required fields below and attach your Resume/CV. Next steps After applying, one of our recruiters will be in touch with you. About us We are committed and skilled software engineers, product designers, and marketing experts who are passionate about developer productivity. We take pride in delivering products that are relied upon daily by some of the world's leading software organizations, such as Netflix, LinkedIn, Airbnb, Spotify, and SAP. Our team is globally distributed but deeply connected. We value our interpersonal relationships as much as we value our achievements. We are a diverse and inclusive workplace where we learn from each other and together. We welcome people of different backgrounds, experiences, abilities, and perspectives. Visit our careers page to learn more about the company and see other open positions. Visit Glassdoor to read what current and former Gradle employees have to say about the company. Privacy Notice For information about our collection, use, and disclosure of applicants’ personal information as well as applicants’ rights over their personal information, please see our Job Applicant Privacy Notice. APPLY ON THE COMPANY WEBSITE To get free remote job alerts, please join our telegram channel “Global Job Alerts” or follow us on Twitter for latest job updates. Disclaimer:  - This job opening is available on the respective company website as of 5thJuly 2023. The job openings may get expired by the time you check the post. - Candidates are requested to study and verify all the job details before applying and contact the respective company representative in case they have any queries. - The owner of this site has provided all the available information regarding the location of the job i.e. work from anywhere, work from home, fully remote, remote, etc. However, if you would like to have any clarification regarding the location of the job or have any further queries or doubts; please contact the respective company representative. Viewers are advised to do full requisite enquiries regarding job location before applying for each job.   - Authentic companies never ask for payments for any job-related processes. Please carry out financial transactions (if any) at your own risk. - All the information and logos are taken from the respective company website. Read the full article

[xceltecseo]

What is AndroidX and Why It is Important to Migrate to AndroidX

ADMIN IN ANDROID, ANDROID APPS BLOG, ANDROIDX, APPLICATION DEVELOPMENT, APPS 

If you're unfamiliar with the phrase, AndroidX is a brand-new open-source initiative that Google is introducing to package libraries with Jetpack. In short, Google decided to start cleaning up their act and utilise a new approach along with new library names because the old method of managing libraries was becoming difficult.

AndroidX Overview

The Android team leverages the new open-source project called AndroidX to create, test, and distribute libraries for Jetpack.

A significant improvement over the original Android Support Library is AndroidX. Similar to the Support Library, AndroidX is developed separately from the Android OS and offers backward compatibility between different Android releases. By offering feature parity and additional libraries, AndroidX completely replaces the Support Library. Additionally, AndroidX has the following capabilities:

All AndroidX packages are located in a single namespace that begins with the letters android x. The comparable AndroidX.* packages have been mapped to the Support Library packages. See the Package Refactoring page for a complete mapping of all the old classes and build objects to the new ones.

AndroidX packages, in contrast to the Support Library, are independently updated and maintained. Beginning with version 1.0.0, the AndroidX packages strictly adhere to semantic versioning. AndroidX libraries in your app can be freely updated.

The AndroidX library will be where all future Support Library work takes place. This entails updating the original Support Library objects and adding fresh Jetpack elements.

Why migrate to AndroidX?

The support library is no longer being maintained and is now at version 28.0.0. Therefore, moving to AndroidX is crucial and necessary if we want bug fixes or new features that would previously have been included in the Support Library. The AndroidX namespace will be used for the release of all new Jetpack libraries.

There are a lot of benefits to switching from Android Support Library to AndroidX. The most recent version information is below:

Android 10 (API level 29)*

Until August 3, 2020, new apps must comply.

required for app updates on November 2, 2020

Better package management:

You get better consistent naming, more regular releases, and independent yet standardised versioning with AndroidX. Other libraries, such as Google Play services, Firebase, Butterknife, Databinding Mockito, and SQL Delight, have switched to using the AndroidX namespace libraries.

Migration is mandatory:

The AndroidX namespace will be used for the release of all new Jetpack libraries. You must switch to the AndroidX namespace in order to utilise features like Jetpack Compose or CameraX, for instance.

Hassle-free App Architecture:

If you want to create an app using Google's Single-Activity Architecture recommendation, you must use the Jetpack Navigation Component.

Google recommended arch:

MVVM pattern combined with Repos and Arch Components. To make the code base scalable, maintainable, and to get better CC, it is inevitable to create big scale programmes using a modular architecture to isolate via modules. Writing exams is made simple.

Conclusion:

There is no getting around this migration because the support library artefacts are being deprecated and all future development is moving to AndroidX. XcelTec is the best option if you want to transfer an existing Android app to Android X. We are a software company that has long offered the top mobile and web solutions.

Little about XcelTec:

To fulfil its purpose of "Delivering Excellence in Technology," XcelTec consistently transforms customer needs into innovative and worthwhile solutions.

We are a tech company that offers business solutions for offshore software development and software outsourcing. Microsoft technology, E-commerce, M-commerce, mobile development, and open source technology are all areas where XcelTec thrives.

By establishing a foundation of work ethics and continuous progress, we uphold honesty, the degree of fulfilment, and dependability with our deeply valued consumers. We can confidently and with great pride say that we are moving in the direction of our mission.

At our company, we are well aware that consumers are looking for employees that can fully understand their problems and logically provide clever digital solutions. XcelTec is aware that our customer wants to make things simple for everyone, whether it be their end customers, vendors, associates, or workers.

Sources:

Migrating to AndroidX: The time is right! Let’s summarize it!

AndroidX Support in React Native Apps

Visit to explore more on What is AndroidX and Why It is Important to Migrate to AndroidX

Get in touch with us for more! 

Contact us on:- +91 987 979 9459 | +1 919 400 9200

Email us at:- sales@xceltec.com

[dailyupdatesarticle]

The best and super comprehensive blog on androidX

[dexfm]

078: TextView

@ttuusskkさんをゲストに迎えて、TextViewのパフォーマンスやPrecomputeText、Bidi、中華フォント問題、絵文字の話などをしました。

podcast feedを購読するか、DLしてお楽しみ下さい。

Show Notes:

Best practice for text on Android and its internals. - DroidKaigi 2019

DroidKaigi 2019 Android Textのセッションの補足 - Qiita

PrecomputedText  |  Android Developers

PrecomputedTextCompat  |  Android Developers

Google I/O 2019 - Best Practices for Using Text in Android

[Android Developers Blog: What’s new for text in Android Q https://android-developers.googleblog.com/2019/07/whats-new-for-text-in-android-q.html]

絵文字を支える技術の紹介 - Qiita

ICU4J Android Framework API  |  Android Developers

Android Dev Summit  |  Android Developers

Contact:

@dexfmpodcast

@hydrakecat

@ttuusskk

[odapplications-blog]

What is AndroidX

[xceltectechnology]

What is AndroidX and Why It is Important to Migrate to AndroidX

If you haven’t heard the term yet, AndroidX is the new open-source project being rolled out by Google to package libraries with Jetpack. Basically, the old way of managing libraries was becoming complicated and so Google decided to start cleaning up their act and use a new system, along with new library terms.

AndroidX Overview

AndroidX is the new open-source project that the Android team uses to develop, test, and package, version, and release libraries within Jetpack.

AndroidX is a major enhancement to the original Android Support Library. Like the Support Library, AndroidX crafts independently from the Android OS and delivers backward-compatibility across Android releases. AndroidX fully replaces the Support Library by providing feature equivalence and new libraries.

In addition, AndroidX includes the following features:

All packages in AndroidX live in a consistent namespace starting with the string android x. The Support Library packages have been mapped into the equivalent AndroidX.* packages. For a full mapping of all the old classes and build objects to the new ones, see the Package Refactoring page.

Unlike the Support Library, AndroidX packages are independently maintained and updated. The AndroidX packages use strict Semantic Versioning starting with version 1.0.0. You can update AndroidX libraries in your project independently.

All new Support Library development will occur in the AndroidX library. This includes maintenance of the original Support Library artefacts and the introduction of new Jetpack components.

Why migrate to AndroidX?

The final version of the support library is 28.0.0 and it’s no longer maintained. So, if we want bug fixes or new features that would have previously gone into the Support Library, It is important and mandatory to migrate to AndroidX. All new Jetpack libraries will be released in AndroidX namespace.

There are many reasons to migrate Android Support Library to AndroidX – The latest version details are below:

Android 10 (API level 29)*

August 3, 2020: Required for new apps

November 2, 2020: Required for app updates

Better package management:

With AndroidX, you get standardized and independent versioning, as well as better standardized naming and more frequent releases. Other libraries have migrated to use the AndroidX namespace libraries, including Google Play services, Firebase, Butter knife, Data binding Miskito, and SQL Delight among others.

Migration is mandatory:

All new Jetpack libraries will be released in AndroidX namespace. So, for example, to take advantage of Jetpack Compose or CameraX, you need to migrate to the AndroidX namespace.

Hassle-free App Architecture:

Jetpack Navigation Component is imperative to follow Google recommended Single-Activity Architecture app approach.

Google recommended arch:

MVVM pattern with Repos, as well as Arch Components. They’re inevitable to build large scale apps in the modular arch to isolate via modules to make the code base maintainable, scalable, and to get better CC. Writing tests made easy.

Conclusion:

The support library artefacts are being deprecated and all future development is going into AndroidX, so there’s no avoiding this migration. If you want to migrate your existing Android app to the Android X; XcelTec is the right choice for you. We are a tech firm providing the best solution on the web and mobile for many years.

Little about XcelTec:

XcelTec operates following the mission of “Delivering Excellence in Technology” by constantly converting customer’s requirements into creative & valuable solutions.

We are a tech firm providing enterprise solutions in software outsourcing and offshore software development. XcelTec excels in every aspect of Microsoft technology, E-commerce, M-commerce, mobile development, and open source technology.

We uphold forthrightness, the extent of fulfilment & reliability with our much-appreciated customers by creating a mainstay of work ethics, and constant improvement. With immense pride and confidence, we can state that we are positively treading the same path matching our mission.

Get in touch with us for more!

Contact us on:- +91 987 979 9459 | +1 919 400 9200

Email us at:- sales@xceltec.com

[softwaretestingexperience]

As the org grew, the time it took to run our automated suite of unit tests went from 30 to 75 minutes. What started as the effort of a handful of engineers had increased to 400 modules and 900,000 lines of code. Maintaining a high bar of quality with this much code requires a continuous investment in testing.  This year, we spun up a Mobile Foundation team and let them loose on our mobile testing infrastructure. We want to share how we scaled our CI pipeline, which is built on top of an in-house task runner called Changes to better serve the 3x growth of new engineers, new features and of course, new tests. Using industry standard tools, some code borrowed from AndroidX, and lots of Kotlin, we reduced our CI runtime from an average of 75 minutes to 25 minutes. We did this by learning a lot about Gradle, offloading work to Firebase Test Lab, and rearchitecting our CI jobs to better allow parallelism.

[freeudemycourses]

[100% OFF] Learn Android the Easy Way: Build a Real App What you Will learn ? You Will Build A Real World TaskNote Android App Using AndroidX, SQLite, ListView, CursorAdapter…

[sukritinfotech]

Flutter Vs React Native: Which One To Choose For Mobile App Development?

Remember the time when the mobile app development services were only bounded towards developing the applications separately, for iOS and Android, but the time has now and so is the technology. There is a whole new different level of technicality in today’s era. The mobile app development companies have grown itself to such a level that now they are not only working but also excelling in development of a single application that will support both Android as well as Iphone. That is where the ends up being a great opportunity for themselves and their investors as well. This system of app development is now trendy since the Facebook used it for the very first time, the development framework, called React Native back in 2015.

Ever since then, businesses had been shifting to the framework after getting a only-for-profit answer to the question ‘Is React Native the best Platform for Your Next App?’. Thus, without an ounce of suspicion,React Native earned the popularity and the leading sites like LinkedIn, Instagram, Walmart and many others shifted to this platform.

In March 2018, Google in the Mobile World Congress announced the beta release of its own program SDK called Flutter. And, in just a few months, Flutter for mobile app development has already began to smashing the React Native for its decent lot of spotlight, supported by the abilities that Google has conveyed upon it in the form of the attributes like Support for AndroidX, Game Controller, and many more.

Momentarily, flutter and React Native have gone into a direct war of mass adoption. Let us look at what the two frameworks are? And their details for the best comparison too.

What is Flutter? Flutter Engine is one of the leading open-source cross-platform apps development frameworks that is operating in today’s industry. It was developed by Google in the year 2017.

For better knowledge, knowing about the advantages, disadvantages or its pros and cons are important.Thus, cited below:

Advantages or Pros: • A full fledged development ecosystem • Highly customizable and can be personalized too • Google makes it extremely reliable • Hot Reload functionality • Open-source and available to use with no restrictions.

Disadvantages or Cons- • A bit Large application size than usual • Reliable on native tools and technologies for building apps

The apps which has been made using this framework includes– Alibaba, OfflinePal, Hamilton, etc.

What is React Native? It is an open-source framework which was developed by the famous Facebook in the year 2015 as its own cross-platform app development technology. It allows the creators to employ React and JavaScript in addition to native platform proficiency expected to build mobile apps.For better knowledge, knowing about the advantages, disadvantages or its pros and cons are important.Thus, cited below:

Advantages or Pros:

• Execution of Native UI components • Ready-made segments • Gives permit to native functionalities • Hot reload • Highly credible • Platform distinct code • Open source • React Native is used for Web functionality

Disadvantages or Cons: • Non seamless navigation • Complicated UI

The apps which has been made using this framework includes: Facebook, Skype, Artsy, Vogue, and Tesla, etc.

The Difference Between Flutter and React Native:

Programming Language- React Native: Uses JavaScript which indicates it is understandable for web developers to transition instantly to React Native for mobile app development as rejected by Dart.

Flutter: Except for the fact that it’s an entire new language and that Dart wasn’t utilized much, it’s loosely established on Java due to abstract object-oriented support. Also, it has some easy to follow documentation rules which are necessary to get you started.

Installation-

React Native: Can be put in using Node Package Manager (NPM) while for using macOS you need to possess the Homebrew package manager as well. So for developers having NPM launched the procedure is really simple whereas other developers would need to comprehend the mechanics and working of NPM.

Flutter: Supports binary download upright from GitHub for a particular platform. Also in the case of macOS after downloading the file that needs to be added as a PATH variable.

UI Component and Development API-

React Native: depends heavily on third-party libraries to access most of the native modules.

Flutter: Rich set of components includes in itself, each native module required hence, eliminates the necessity of a third-party library. Also, Flutter has ample of WIDGETS.

Community Support-

React Native: Being the framework which was published first out of the two, it is looming to get a good amount of support and it surely did since 2015 as it is strongly preserved by the creator on GitHub and from many more communities all around the globe.

Flutter: Flutter too is on a rapid boost in terms of community support but then again it will take some requisite lot of time for its resources to be made available which will ultimately encourage the developers to solve common issues.

Testing Support-

React Native: Again it highly relies upon the third-party tools for integration and UI testing.

Flutter: Flutter has its own elements to test apps at 3 different levels which are as follows- unit test, widget test and integration test.

Build & Release Automation Support-

React Native: Documentation for self-regulating deployment of apps from any platform isn’t furnished.So basically you are on your own to search and deploy it on Play Store or App Store.

Flutter: It has deployment backing through CLI and also a documentation for deployment process with fast lane.

DevOps and CI/CD Support-

React Native: Does not contain the official documentation on setting up CI/CD.

Flutter: Has an independent article on CI and testing which one can view. However, setting up CI/CD using Flutter CLI is relatively easy.

However, most of the industry chiefs believe Flutter to be the new best framework for mobile app development. Considering the points above, Flutter has won the cross-platform mobile app development contest reasonably strongly. It has all the capabilities to develop a beautiful mobile apps and also assist businesses in no time. Flutter framework is not going to end soon and it does have an impressive future.

[jacob-cs]

android jetpack viewmodel

https://stackoverflow.com/a/57630353/3151712

질문) ViewModelProviders is deprecated So what's the alternative to create the ViewModel's object ?

답) 

boardViewModel = ViewModelProvider(this).get(BoardViewModel::class.java)

답)

private val viewModel: EntityGridViewModel by viewModels()

위의 방법으로 사용했지만 constructor가 있는 ViewModel의 경우 위의 구문실행시기가 이른 시기에 해당해서 constructor에 전달될 parameter를 준비하는데 시간이 부족한 경우가 많다. 그래서 다른 방법을 사용하게 되었다. 

https://www.albertgao.xyz/2018/04/13/how-to-add-additional-parameters-to-viewmodel-via-kotlin/

binding.authViewModel = ViewModelProviders.of(  this,  viewModelFactory { MyViewModel("albert") } ).get(AuthViewModel::class.java)

참고자료) passing parameters viewmodel

https://stackoverflow.com/a/60130631/3151712

https://www.albertgao.xyz/2018/04/13/how-to-add-additional-parameters-to-viewmodel-via-kotlin/

.

.

.

https://developer.android.com/topic/libraries/architecture/viewmodel

ViewModel 전반적인 사용 방법

.

.

위와 같이 사용하려고 하였으나 자동완성이 되지 않았다. dependency 설정이 잘못되어있었기 때문이다. 

   // ViewModel //    android docs ref) https://developer.android.com/jetpack/androidx/releases/lifecycle    def lifecycle_version = "2.2.0"    def arch_version = "2.1.0"    implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:$lifecycle_version"    // LiveData    implementation "androidx.lifecycle:lifecycle-livedata-ktx:$lifecycle_version" //    ref) https://developer.android.com/kotlin/ktx#fragment    implementation "androidx.fragment:fragment-ktx:1.2.5"    //ViewModel //    from codelab ref) https://codelabs.developers.google.com/codelabs/kotlin-android-training-view-model/index.html?index=..%2F..android-kotlin-fundamentals#4    implementation 'androidx.lifecycle:lifecycle-extensions:2.0.0'

가 필요했다. 

https://developer.android.com/topic/libraries/architecture/viewmodel#sharing

https://developer.android.com/kotlin/ktx#fragment

implementation "androidx.fragment:fragment-ktx:1.2.5"

.

.

.

.

주의사항)

https://developer.android.com/topic/libraries/architecture/viewmodel

Caution: A ViewModel must never reference a view, Lifecycle, or any class that may hold a reference to the activity context.

.

.

.

.

하나의 activity 아래에 여러개의 fragment가 있고 activity lifecycle에 맞춰서 share view model을 사용하는 방법 

기본적으로 아래 내용은 그대로 이나 약간 문법이 바뀌었다. 

변화된 내용은 https://developer.android.com/topic/libraries/architecture/viewmodel#sharing 에서 확인할수 있다. 변화된 코드는 아래와 같다. 먼저 바로 아래 것을 보고 밑에것을 보면 된다. 

class SharedViewModel : ViewModel() {    val selected = MutableLiveData<Item>()    fun select(item: Item) {        selected.value = item    } } class MasterFragment : Fragment() {    private lateinit var itemSelector: Selector    // Use the 'by activityViewModels()' Kotlin property delegate    // from the fragment-ktx artifact    private val model: SharedViewModel by activityViewModels()    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {        super.onViewCreated(view, savedInstanceState)        itemSelector.setOnClickListener { item ->            // Update the UI        }    } } class DetailFragment : Fragment() {    // Use the 'by activityViewModels()' Kotlin property delegate    // from the fragment-ktx artifact    private val model: SharedViewModel by activityViewModels()    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {        super.onViewCreated(view, savedInstanceState)        model.selected.observe(viewLifecycleOwner, Observer<Item> { item ->            // Update the UI        })    } }

.

https://medium.com/mindorks/how-to-communicate-between-fragments-and-activity-using-viewmodel-ca733233a51c

Here comes ViewModel to rescue us from handling a lot of scenario and implementing interface . We only need to create ViewModel class and create instance in fragment but using the activity scope so that it will be available for all the fragment of the activity including activity itself.

Create a ViewModel class

class SharedViewModel:ViewModel(){    val inputNumber = MutableLiveData<Int>() }

To emit or pass data from our input fragment create ViewModel in activity scope. To do this we have to pass the activity reference as argument of the ViewModelProvides.of() method. Noe just pass the data to ViewModel object like this

activity?.let {    sharedViewModel = ViewModelProviders.of(it).get(SharedViewModel::class.java) } et_input.addTextChangedListener(object : TextWatcher {    override fun afterTextChanged(p0: Editable?) {}    override fun beforeTextChanged(p0: CharSequence?, p1: Int, p2: Int, p3: Int) {}    override fun onTextChanged(txt: CharSequence?, p1: Int, p2: Int, p3: Int) {        txt?.let {            var input = 0            if (txt.toString().isNotEmpty()) {                input = txt.toString().toInt()            }            sharedViewModel?.inputNumber?.postValue(input)        }    }

In the activity we just need to create instance of our ViewModel and observe the required data like this

val sharedViewModel = ViewModelProviders.of(this).get(SharedViewModel::class.java) sharedViewModel.inputNumber.observe(this, Observer {    it?.let {        // do some thing with the number    } })

Now what about output fragment? We can do same for the output fragment to observe the data. But keep in mind that we need create the ViewModel instance in activity scope, otherwise android will create a separate instance rather than sharing the same instance and we will not get the data.

For output fragment do it like this

activity?.let {    val sharedViewModel = ViewModelProviders.of(it).get(SharedViewModel::class.java)    sharedViewModel.inputNumber.observe(this, Observer {    it?.let {            // do some thing with the number        }    }) }

That’s it. Source code can be found here.

.

source code

class InputFragment : Fragment() {    private var sharedViewModel: SharedViewModel? = null    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View? {        return inflater.inflate(R.layout.fragment_input, container, false)    }    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {        activity?.let {            /**             *  create view model in activity scope             */            sharedViewModel = ViewModelProviders.of(it).get(SharedViewModel::class.java)        }        et_input.addTextChangedListener(object : TextWatcher {            override fun afterTextChanged(p0: Editable?) {}            override fun beforeTextChanged(p0: CharSequence?, p1: Int, p2: Int, p3: Int) {}            override fun onTextChanged(txt: CharSequence?, p1: Int, p2: Int, p3: Int) {                txt?.let {                    var input = 0                    if (txt.toString().isNotEmpty()) {                        input = txt.toString().toInt()                    }                    sharedViewModel?.inputNumber?.postValue(input)                }            }        })    } }

package ninja.shuza.sharedviewmodel import android.arch.lifecycle.Observer import android.arch.lifecycle.ViewModelProviders import android.support.v7.app.AppCompatActivity import android.os.Bundle import kotlinx.android.synthetic.main.activity_main.* import kotlin.properties.Delegates class MainActivity : AppCompatActivity() {    override fun onCreate(savedInstanceState: Bundle?) {        super.onCreate(savedInstanceState)        setContentView(R.layout.activity_main)        supportFragmentManager.beginTransaction().add(R.id.layout_top, InputFragment()).commit()        supportFragmentManager.beginTransaction().add(R.id.layout_bottom, OutputFragment()).commit()        val message = resources.getString(R.string.show_input)        val sharedViewModel = ViewModelProviders.of(this).get(SharedViewModel::class.java)        sharedViewModel.inputNumber.observe(this, Observer {            it?.let {                tv_show_input.text = "$message  $it"            }        })    } }

package ninja.shuza.sharedviewmodel import android.arch.lifecycle.Observer import android.arch.lifecycle.ViewModelProviders import android.os.Bundle import android.support.v4.app.Fragment import android.view.LayoutInflater import android.view.View import android.view.ViewGroup import kotlinx.android.synthetic.main.fragment_output.* /** * * :=  created by:  Shuza * :=  create date:  09-Aug-2018 * :=  (C) CopyRight Shuza * :=  www.shuza.ninja * :=  shuza.sa@gmail.com * :=  Fun  :  Coffee  :  Code * **/ class OutputFragment : Fragment() {    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View? {        return inflater.inflate(R.layout.fragment_output, container, false)    }    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {        /**         *  create view model in activity scope         */        activity?.let {            val sharedViewModel = ViewModelProviders.of(it).get(SharedViewModel::class.java)            observeInput(sharedViewModel)        }    }    private fun observeInput(sharedViewModel: SharedViewModel) {        sharedViewModel.inputNumber.observe(this, Observer {            it?.let {                tv_output.text = "2 x $it  =  ${2 * it}"            }        })    } }

.

.

.

.

share viewmodel with several fragment

original source : https://medium.com/mindorks/how-to-communicate-between-fragments-and-activity-using-viewmodel-ca733233a51c

Here comes ViewModel to rescue us from handling a lot of scenario and implementing interface . We only need to create ViewModel class and create instance in fragment but using the activity scope so that it will be available for all the fragment of the activity including activity itself.

Create a ViewModel class

class SharedViewModel:ViewModel(){    val inputNumber = MutableLiveData<Int>() }

To emit or pass data from our input fragment create ViewModel in activity scope. To do this we have to pass the activity reference as argument of the ViewModelProvides.of() method. Noe just pass the data to ViewModel object like this

activity?.let {    sharedViewModel = ViewModelProviders.of(it).get(SharedViewModel::class.java) } et_input.addTextChangedListener(object : TextWatcher {    override fun afterTextChanged(p0: Editable?) {}    override fun beforeTextChanged(p0: CharSequence?, p1: Int, p2: Int, p3: Int) {}    override fun onTextChanged(txt: CharSequence?, p1: Int, p2: Int, p3: Int) {        txt?.let {            var input = 0            if (txt.toString().isNotEmpty()) {                input = txt.toString().toInt()            }            sharedViewModel?.inputNumber?.postValue(input)        }    }

In the activity we just need to create instance of our ViewModel and observe the required data like this

val sharedViewModel = ViewModelProviders.of(this).get(SharedViewModel::class.java) sharedViewModel.inputNumber.observe(this, Observer {    it?.let {        // do some thing with the number    } })

Now what about output fragment? We can do same for the output fragment to observe the data. But keep in mind that we need create the ViewModel instance in activity scope, otherwise android will create a separate instance rather than sharing the same instance and we will not get the data.

For output fragment do it like this

activity?.let {    val sharedViewModel = ViewModelProviders.of(it).get(SharedViewModel::class.java)    sharedViewModel.inputNumber.observe(this, Observer {    it?.let {            // do some thing with the number        }    }) }

That’s it. Source code can be found here.

[concettolabs]

Android Studio 4.0 New Features Preview

Today, Android has over 2.5 billion monthly active devices. The Android developers are using IDEs to build on Android using the latest features. Android Studio 3.6 released in February with a bunch of useful features. Google pushed Android Studio 4.0 with more convenient features & required fixes. The features it adds are:

Motion Editor

Build Speed Window

Live Layout Inspector

Layout Multi Preview

Kotlin DSL Script files

Smart Editor for R8 Rules

The user can download Android Studio 4.0 for Mac, Windows, and Linux from developer.android.com/studio. Here, the number 4.0 tells that it’s a significant release for anyone who wants to build apps and games for Android.

To offer a better understanding, we have broken down the features by categories. Such as Design, Develop, and Build. Moreover, the new version will help in improvements and bug fixes. Dive in to know more.

Android Studio 4.0 Design Features

1. Motion Editor

Motion Editor is the first feature that we’ll talk about. AndroidX has a subclass of ConstraintLayout called as MotionLayout. MotionLayout’s helps in animation between layout states. It creates transitions in XML to resolve problems. The new Motion Editor interface lets you create visual transitions in a MotionLayout. Check below XML file where you don’t have to write code yourself.

2. Upgraded Layout Inspector

Layout Inspector is an essential tool that let you see how your app laid out. Whether on-screen or along with different attributes. Layout Inspector expands on the old version using the improved feature. You can still access its simple view-tree inspection. Which includes features like live refreshing. Check the 3D representation of what’s on-screen.

3. Layout Validation

User can create a layout using a built-in preview in Android Studio. Switching to different screen sizes and resolutions in the preview can bother you. With Android Layout Validation view, you can look on a variety of different screen sizes. And the resolution in the preview. For getting started, the user needs to click on the Layout Validation tab in the top-right corner of IDE.

Android Studio 4.0 Develop Features

1. Smart Editor while writing rules for Code Shrinking

R8 introduce in Android plugin 3.4. It combines shrinking, desugaring, optimizing, and dexing. It results in noticeable build in performance improvements. While creating R8, Android studio provides a smart editor. It integrates Android projects to ensure full completion of class, methods, fields, and navigations.

2. CPU Profiler UI Upgrades

CPU profiler designed to have an abundant amount of data about app thread activity and trace recording. The recording spread from the main profiler timeline and organized in groups. One can move the group up and down within a group for extra customization. Google redesign system Trace UI that offers better visual distinction. It focuses on seeing data for threads you choose. With this significant decrease in error, rates reported by Google.

3. IntelliJ IDEA 2019.3 Platform Update

Android Studio IDE updated the improvement, which mainly focuses on performance and quality. The upgrades add IntelliJ IDEA 2019.3 and 2019.3.3 releases.

4. Clang Support for C++

Clang is primary language analysis engine. It’s used for inspection, navigation, completion and other warnings. The user finds bundle clang-tidy in Android Studio added by Google. One can configure Clangd by: Go to the IDE settings dialog> navigate to language and framework> C/C++ >Clangd and configure the options.

5. Kotlin Android Live Templates

The feature allows inserting standard code with typing simple keywords. The Android studio covers live templates for Kotlin code. Example type ‘toast’ and press insert key. Full live template list will show. Or navigate to Editor> Live Templates in the settings dialog.

Android Studio 4.0 Build Features

1. Build Analyzer

The outdated task can take longer build times which led to low productivity. The Build Analyzer feature will help the developer to understand the job. The highlighted plugin responsible for build time and suggests steps to mitigate regressions. Hire android app developer who has a better understanding of the platform.

2. Feature to Feature Dependencies

The dynamic feature module depends on another element to define the relationship. It ensures that your app uses another feature module to unlock additional functionalities. It results in fewer requests and easier modularization of your app.

3. Java 8 Language Library desugaring in D8 and R8

It’s one of the annoying parts of Android development that used in Java 8 features. Android Gradle supports various Java 8 language features. Such as lambda expressions, and method references called as desugaring. Regardless, it uses standard language APIs which previously available in recent releases.

4. New options to enable and disable build features

Android Gradle has in-built support for modern libraries. Which includes data binding, view binding and build features with auto-generated BuildConfig classes. You needn’t use all features and libraries for every project. You have to optimize the build in performance for larger projects.

5. Essential Support for Kotlin DSL Script files

Android 4.0 comes with support for Kotlin DSL that builds script files(*.kts) with a full suite of quick fixes. Refine the Android Gradle, which results in breaking API for Kotlin script users. It can fix and make more idiomatic with easy to use DSL for Kotlin Script users.

6. Metadata Dependencies

Android 4.0 comes with metadata plugins. It shows the library dependencies compiled into your app. Whenever you’re uploading your application metadata provides alerts for SDKs and dependencies. In a few cases, it also provides actionable feedback to resolve those issues. The data compressed, encrypted by Google play, and stored in the signing block of your released app.

Closure

To get a better understanding, watch the video, and help developers “code smarter, build faster-designed apps. Android Application Development Company to update your existing installation from within the app.

[androiddevtutorial]

🛑Stop right there! 🛑 Similar to the January 8 article, #NowInAndroid is now available in video form! Join @chethaase in this ongoing guide to what's new in Android development. This time: AndroidX release, Room and KTX docs, and more. 👀 → https://t.co/KI2cDdo4aI https://t.co/gUzIqKiHxc

[workfromhomeyoutuber]

Ad-Hoc Labs: Sr. Android Developer

Headquarters: Los Angeles URL: https://www.adhoclabs.co/

Description

We are looking for a remote Android Developer to join a small, committed technical team at Ad Hoc Labs, makers of the Burner & Firewall apps. We empower people to take control over their identity and privacy by giving them fully functional, powerful, and reliable second phone numbers.

As an Android Developer, you will be writing code to build new features, execute user interfaces, and help maintain and improve the current codebase. Since we are a small team, you will also have the opportunity to learn new technologies and contribute directly to the development of a product that millions of people rely on to help protect their privacy.

RESPONSIBILITIES INCLUDE:

Development of native Android app while working on an agile team

Support the entire application lifecycle (concept, design, test, release and support)

Write clean, maintainable native application code for Android

Ensure app performance, quality, and responsiveness

Package apps for deployment to Google Play Store and help with automation tasks

Transform designs into awesome and functional user experiences

Keep up to date knowledge of emerging Android technologies

SKILLS + QUALIFICATIONS:

3+ years with Kotlin or Java and Android SDK

Worked on at least one application published to the Google Play store

Experience with the various means of automated testing (junit4/5, robolectric, espresso)

Experience with modern mobile software design patterns (MVP, MVI, MVVM, etc)

Knowledge of popular 3rd party Android tools and apis

Experience with RXJava, Kotlin Coroutines, Dagger2, AndroidX (lifecycle, workmanager, etc)

Ability to diagnose problems and solve them independently

Experience working with distributed, agile teams

Experience with Google Play Billing is a bonus

WHAT WE OFFER YOU:

Meaningful work on an innovative and growing set of products

Collaborative, cross-functional work culture with an emphasis on autonomy and communication

Health and Dental coverage for employees, dependents & domestic partners

Investment in career development, including training, conferences, and online learning resources

 Ad Hoc Labs is committed to building a diverse, inclusive company and encourages applications from candidates of all backgrounds.

 Ad Hoc Labs, Inc. is an equal employment opportunity employer and makes employment decisions on the basis of merit. We seek to employ the most qualified person in every job. Ad Hoc Labs, Inc. does not discriminate on the basis of sex, gender (including pregnancy, childbirth, breastfeeding or related medical conditions), gender identity, gender expression, age, color, race, religion, marital status, national origin, ancestry, sexual orientation, physical & mental disability, medical condition, genetic information, military and veteran status, or any other basis protected by federal, state or local law. Applicants with disabilities may be entitled to reasonable accommodation under the terms of the Americans with Disabilities Act and certain state or local laws.

To apply: https://hire.withgoogle.com/public/jobs/adhoclabsco/view/P_AAAAAAFAAAQKQMCq7Vy_Qv

from We Work Remotely: Remote jobs in design, programming, marketing and more https://ift.tt/2TqyA9Y from Work From Home YouTuber Job Board Blog https://ift.tt/2svnMw6

[t-baba]

Getting Started with the React Native Navigation Library

One of the most important aspects of React Native app development is the navigation. It’s what allows users to get to the pages they’re looking for. That’s why it’s important to choose the best navigation library to suit your needs.

If your app has a lot of screens with relatively complex UI, it might be worth exploring React Native Navigation instead of React Navigation. This is because there will always be performance bottlenecks with React Navigation, since it works off the same JavaScript thread as the rest of the app. The more complex your UI, the more data has to be passed to that bridge, which can potentially slow it down.

In this tutorial, we’ll be looking at the React Native Navigation library by Wix, an alternative navigation library for those who are looking for a smoother navigation performance for their React Native apps.

Prerequisites

Knowledge of React and React Native is required to follow this tutorial. Prior experience with a navigation library such as React Navigation is optional.

App Overview

In order to demonstrate how to use the library, we’ll be creating a simple app that uses it. The app will have five screens in total:

Initialization: this serves as the initial screen for the app. If the user is logged in, it will automatically navigate to the home screen. If not, the user is navigated to the login screen.

Login: this allows the user to log in so they can view the home, gallery, and feed. To simplify things, the login will just be mocked; no actual authentication code will be involved. From this screen, the user can also go to the forgot-password screen.

ForgotPassword: a filler screen, which asks for the user’s email address. This will simply be used to demonstrate stack navigation.

Home: the initial screen that the user will see when they log in. From here, they can also navigate to either the gallery or feed screens via a bottom tab navigation.

Gallery: a filler screen which shows a photo gallery UI.

Feed: a filler screen which shows a news feed UI.

Here’s what the app will look like:

You can find the source code of the sample app on this GitHub repo.

Bootstrapping the App

Let’s start by generating a new React Native project:

react-native init RNNavigation --version react-native@0.57.8

Note: we’re using a slightly older version of React Native, because React Native Navigation doesn’t work well with later versions of React Native. React Native Navigation hasn’t really kept up with the changes in the core of React Native since version 0.58. The only version known to work flawlessly with React Native is the version we’re going to use. If you check the issues on their repo, you’ll see various issues on version 0.58 and 0.59. There might be workarounds on those two versions, but the safest bet is still version 0.57.

As for React Native version 0.60, the core team has made a lot of changes. One of them is the migration to AndroidX, which aims to make it clearer which packages are bundled with the Android operating system. This essentially means that if a native module uses any of the old packages that got migrated to the new androidx.* package hierarchy, it will break. There are tools such as jetifier, which allows for migration to AndroidX. But this doesn’t ensure React Native Navigation will work.

Next, install the dependencies of the app:

react-native-navigation — the navigation library that we’re going to use.

@react-native-community/async-storage — for saving data to the app’s local storage.

react-native-vector-icons — for showing icons for the bottom tab navigation.

yarn add react-native-navigation @react-native-community/async-storage react-native-vector-icons

In the next few sections, we’ll be setting up the packages we just installed.

Setting up React Native Navigation

First, we’ll set up the React Native Navigation library. The instructions that we’ll be covering here are also in the official documentation. Unfortunately, it’s not written in a very friendly way for beginners, so we’ll be covering it in more detail.

Note: the demo project includes an Android and iOS folders as well. You can use those as a reference if you encounter any issues with setting things up.

Since the name of the library is very long, I’ll simply refer to it as RNN from now on.

Android Setup

In this section, we’ll take a look at how you can set up RNN for Android. Before you proceed, it’s important to update all the SDK packages to the latest versions. You can do that via the Android SDK Manager.

settings.gradle

Add the following to your android/settings.gradle file:

include ':react-native-navigation' project(':react-native-navigation').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-navigation/lib/android/app/')

Gradle Wrapper Properties

In your android/gradle/wrapper/gradle-wrapper.properties, update Gradle’s distributionUrl to use version 4.4 if it’s not already using it:

distributionUrl=https\://services.gradle.org/distributions/gradle-4.4-all.zip

build.gradle

Next, in your android/build.gradle file, add mavenLocal() and mavenCentral() under buildscript -> repositories:

buildscript { repositories { google() jcenter() // add these: mavenLocal() mavenCentral() } }

Next, update the classpath under the buildscript -> dependencies to point out to the Gradle version that we need:

buildscript { repositories { ... } dependencies { classpath 'com.android.tools.build:gradle:3.0.1' } }

Under allprojects -> repositories, add mavenCentral() and JitPack. This allows us to pull the data from React Native Navigation’s JitPack repository:

allprojects { allprojects { repositories { mavenLocal() google() jcenter() mavenCentral() // add this maven { url 'https://jitpack.io' } // add this } }

Next, add the global config for setting the build tools and SDK versions for Android:

allprojects { ... } ext { buildToolsVersion = "27.0.3" minSdkVersion = 19 compileSdkVersion = 26 targetSdkVersion = 26 supportLibVersion = "26.1.0" }

Lastly, we’d still want to keep the default react-native run-android command when compiling the app, so we have to set Gradle to ignore other flavors of React Native Navigation except the one we’re currently using (reactNative57_5). Ignoring them ensures that we only compile the specific version we’re depending on:

ext { ... } subprojects { subproject -> afterEvaluate { if ((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) { android { variantFilter { variant -> def names = variant.flavors*.name if (names.contains("reactNative51") || names.contains("reactNative55") || names.contains("reactNative56") || names.contains("reactNative57")) { setIgnore(true) } } } } } }

Note: there are four other flavors of RNN that currently exist. These are the ones we’re ignoring above:

reactNative51

reactNative55

reactNative56

reactNative57

android/app/build.gradle

On your android/app/build.gradle file, under android -> compileOptions, make sure that the source and target compatibility version is 1.8:

android { defaultConfig { ... } compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 } }

Then, in your dependencies, include react-native-navigation as a dependency:

dependencies { implementation fileTree(dir: "libs", include: ["*.jar"]) implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}" implementation "com.facebook.react:react-native:+" implementation project(':react-native-navigation') // add this }

Lastly, under android -> defaultConfig, set the missingDimensionStrategy to reactNative57_5. This is the version of RNN that’s compatible with React Native 0.57.8:

defaultConfig { applicationId "com.rnnavigation" minSdkVersion rootProject.ext.minSdkVersion targetSdkVersion rootProject.ext.targetSdkVersion missingDimensionStrategy "RNN.reactNativeVersion", "reactNative57_5" // add this versionCode 1 versionName "1.0" ndk { abiFilters "armeabi-v7a", "x86" } }

The post Getting Started with the React Native Navigation Library appeared first on SitePoint.

by Wern Ancheta via SitePoint https://ift.tt/34ZFDci

[ussllc-blog]

Google launches Android Studio 3.5 with improved memory settings, build speed, and Apply Changes

Google today launched Android Studio 3.5, the latest version of its integrated development environment (IDE), with a specific focus on “product quality.” This release is the last one under Project Marble, a fancy name for an initiative Google announced late last year to improve Android Studio. For eight months, the team focused “on making the fundamental features and flows of Android Studio & Emulator rock-solid.” All the improvements were either to system health, feature polish, or bug fixes. To improve system health, Google created a new set of infrastructure and internal dashboards to better detect performance problems. The team ultimately fixed over 600 bugs, 50 memory leaks, and 20 IDE hangs and improved XML & Kotlin typing latency. For the Android Emulator, the team decreased the CPU and memory impact. The team also took a look at app deployment flow to a device, replacing Instant Run with Apply Changes. The new system no longer modifies an APK during your build. Instead, it uses runtime instrumentation to redefine classes on the fly.

You can download Android Studio 3.5 for Windows, Mac, and Linux now directly from developer.android.com/studio. If you are already using Android Studio, you can get the latest version in the navigation menu (Help => Check for Update on Windows/Linux and Android Studio => Check for Updates on OS X). Google released Android Studio 3.4 in April. The version number 3.5 would suggest this isn’t a significant release, but if you build for Android, you should probably take a peek at the list below.

Android Studio 3.5 features

Here’s the rundown of what version 3.5 brings to the table: Auto-recommend Memory Settings: The IDE now recognizes when an app project needs more RAM on a machine with higher RAM capacity and will notify you to increase the memory heap size. You can also adjust the settings yourself (Appearance & Behavior => Memory Settings). User Interface Freezes: XML typing has been optimized. Editing data binding expressions in XML is faster due to typing latency improvements. Build Speed: Incremental build support has been added to the top annotation processors including Glide, AndroidX data binding, Dagger, Realm, and Kotlin (KAPT). Incremental support can make a notable impact on build speed. Disk I/O File Access Speed: For Windows users, the default configuration of anti-virus scanners does not optimally exclude build output folders. Android Studio now detects this and helps guide you through the optimal setup. Apply Changes: The new Apply Changes features is a rewrite of Instant Run, which now enables you to quickly see your code edits on an emulator or device without restarting your app is great for app development. Unlike Instant Run, Apply Changes does not modify your APK which means it is reliable and has a predictable behavior. To support the changes, the entire deployment pipeline has been re-architected to improve deployment speed. The run and deployment toolbar buttons have also been tweaked for a more streamlined experience. Android Studio 3.5 also includes the usual performance improvements and bug fixes on top of the new features (full release notes). Google didn’t share its plans for the next version. Read the full article