Android Nougat Reply Notification Demo

Starting in Android 7.0 (API level 24) You have a lot of control, and you’re getting even more. Google has also done some cleanup to make all of those alerts look more refined and add in some color in the right places to make it easier to quickly see the most important information.

From the lock screen, you’ll notice the subtle aesthetic differences, but just as before you can swipe the away or tug down slightly to launch the Quick Reply. To type, you’ll need to unlock the device with the fingerprint reader, PIN, pass-code, or pattern.

With the new notification type introduce in Android 7.0 (Nougat) users can respond directly to text messages or update task lists from within the notification dialog. On a handheld, the inline reply action appears as an additional button displayed in the notification. A user replies via keyboard, the system attaches the text response to the intent you had specified for the notification action and sends the intent to your handheld app.


Lets  Get Started with Tutorial

  • Create an instance of RemoteInput.Builder that you can add to your notification action.

  •  Attach the RemoteInput


  • Apply the action to a notification


Above codes need sending notification.

Read text written on REPLY.

  • Query the bundle using the result key


  • Give another notification using the same notification ID that you provided for the previous notification. The progress indicator disappears from the notification interface to inform users of a successful reply.


Get full example source code on Github

Thank you for reading.

Secure Web-service Url in Android

This is serious problem that every one facing . How to secure Web-service URL if someone decompile the application.

Now a Days there are lots of tool that decompile the apk file and give possible java code. In code we have our Web-service url . Now that person have that url and get to know some important thing that we don’t want to disclose.

Even Using proguard it not Convert String resource to any secure resource.

So I research to that and have one idea that will help to secure our web-services.for that You will require only a single URL that call setup-url will setup all the stuff you want. I divide it in some steps.

Step 1 : Create Explicit Sqlite Database and insert your setup-url in any table and store it in asset folder.

Step 2 : At the Time of Execution store it in your data/data/your package/databases Location.

Step 3 : Now With Your java class File select that url from table.

Step 4 : Now while executing this web-service Pass one POST parameter as Token with it, Now at Web-service it will check first is the call is valid (Means from application) or Not. If yes then application will access the Url as response and then store it locally. If no then It will ask for token or redirect to the forbidden page.

Hope it will help to secure.

All other suggestion are welcome.