Verify that Intent can be launched


// TODO (1) Create a method called openWebPage that accepts a String as a parameter

// Do steps 2 - 4 within openWebPage

    // TODO (2) Use Uri.parse to parse the String into a Uri

    // TODO (3) Create an Intent with Intent.ACTION_VIEW and the webpage Uri as parameters

    // TODO (4) Verify that this Intent can be launched and then call startActivity

public void openWebPage(String url){
    Uri uri = Uri.parse(url);
    Intent intent = new Intent(Intent.ACTION_VIEW,uri);
    if(intent.resolveActivity(getPackageManager()) != null){
        startActivity(intent);
    }
}

When you call startActivity() or startActivityForResult() and pass it an implicit intent, the system resolves the intent to an app that can handle the intent and starts its corresponding Activity. If there's more than one app that can handle the intent, the system presents the user with a dialog to pick which app to use.
This page describes several implicit intents that you can use to perform common actions, organized by the type of app that handles the intent. Each section also shows how you can create an intent filter to advertise your app's ability to perform the same action.

Caution: If there are no apps on the device that can receive the implicit intent, your app will crash when it calls startActivity(). To first verify that an app exists to receive the intent, call resolveActivity() on your Intent object. If the result is non-null, there is at least one app that can handle the intent and it's safe to call startActivity(). If the result is null, you should not use the intent and, if possible, you should disable the feature that invokes the intent.
Source: https://developer.android.com/guide/components/intents-common.html

Bu blogdaki popüler yayınlar

SDLC - Software Development Life Cycle

Resim
SDLC -  Software Development Life Cycle  is a process used by the software industry to design, develop and test high quality softwares. 1- Requirement Analysis 2- Defining Requirements To clearly define and document the product requirements SRS (Software Requirement Specification)   document which consists of all the product requirements to be designed and developed during the project life cycle. 3-   Designing the Product Architecture One design approach for the product architecture is proposed and documented in a DDS - Design Document Specification . DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product. DDS defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules. 4- Developing the ...
Devamı

@SerializedName and @Expose annotations

The  @SerializedName  annotation is needed for Gson to map the JSON keys with our fields. In keeping with Java's camelCase naming convention for class member properties, it is not recommended to use underscores to separate words in a variable.  @SerializedName  helps translate between the two. @SerializedName ( "quota_remaining" ) @Expose private Integer quotaRemaining; In the example above, we are telling Gson that our JSON key  quota_remaining  should be mapped to the Java field  quotaRemaining .  If both of these values were the same, i.e. if our JSON key was  quotaRemaining  just like the Java field, then there would be no need for the  @SerializedName  annotation on the field because Gson would map them automatically. The  @Expose  annotation indicates that this member should be exposed for JSON serialization or deserialization. 
Devamı