I've developed an Android library and successfully uploaded to GitHub.
Here is my GitHub library repo : https://github.com/sangeethnandakumar/TestTube
I'm using JITPACK PACKAGE repository to build the dependency. It works like anything and I deployed around 13 releases (v2.5.3 is the last release).
Here are my Jitpack releases : https://jitpack.io/#sangeethnandakumar/TestTube
I wan't to make this library available via Android Arsenal. I have an account on Android arsenal linked with GitHub. I need to set search tags and description for my library at Android Arsenal.
Link to Android arsenal : https://android-arsenal.com
What can be the steps to do that?
I had the same question once.
There is no as such procedure for that. You have to suggest your project on their website and then after a couple of days, they approve it and it is listed on the website. Go to this url
Android Arsenal Suggestion Url
They don't mail you or send any confirmation aboout the listing of your project. You will have to keep checking everyday the homepage of the andorid arsenal. That is where they list the latest libraries..
Related
I have updated my current play store app with the Instant app appLink feature. But the link is still not working after waited for 4 days.
I have created link with below steps.
Tools -> App Links Assistants
Followed all the steps and Verify that link in android studio.
It verified successfully.
I have added a dependency in app-level Gradle: implementation "com.google.android.gms:play-services-instantapps:17.0.0"
To enable instant app right-click on app module -> Refactor -> Enable instant app support.
Increment a version code to 1 and uploaded a new build on the play store.
Could you guys please help me out to find out the missing element or a direction?
Have you followed the below developer guide for the app asset link?
https://developer.android.com/training/app-links/verify-site-associations
In that, they have mentioned the steps which have to address accordingly.
Also, you can confirm that the Digital Asset Links JSON file is properly hosted and defined using the below URL:
https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://domain.name:optional_port&relation=delegate_permission/common.handle_all_urls
I'm really new with android developing. But I know how to upload a library to GitHub and include it in an android project. Recently, I'm working on some android apps, and I realized that I need to use some layouts and classes for all the apps. So, I created an android library and kept that inside all the project files. Then I came to know that I can simply upload that library to GitHub and use it for all the projects. But I'm not sure if it's a good idea. Is there any advantage if I upload it to GitHub?
In general, using a source control (git or other ones) is always a good idea given that your local filesystem can crash or you may want to revisit certain revisions you made to your project. Github is very popular and hosts several highly used projects, so it is no doubt a good place to upload. However, you must know that if you don't have their paid account, the project will be public (at this time, free accounts don't have a way to create private projects). Are you developing as hobby and do you mind if others see / take the code and reuse (hopefully under the licensing terms you specify)? Or is that something you're doing for an employer? In that case you should consult with the employer if this is OK.
Now as for sharing this module across projects, I don't think github has a secret sauce here. You could always build your library once and drop it in as dependency into all your apps, without having to copy its source code into each project. You may also want to look into integration with maven / gradle build systems, which Android Studio uses. For example, third party libraries often are available as downloadable libraries from maven central, and you can add a couple of lines to your build.gradle to go fetch a specific version of your library from maven central, rather than manually adding that library jar to the project that is using it. If your library code is on github, there are ways to publish to maven central from github ( http://datumedge.blogspot.com/2012/05/publishing-from-github-to-maven-central.html ) but I don't have experience with that step.
I want to add adMob and Google Play Game Services to my app for iOS and android. I know I can do this using bindings. I have been searching online and that is what I have found. However, being new to programming, I cannot find a clear cut tutorial on how to use this, I do not know what a binding is nor how to install RoboVM or what it is. Would anyone be able to help me out on how to use RoboVM to accomplish this with simple and easy to follow steps.
RoboVM is deprecated in favor of RoboPods.
https://github.com/robovm/robovm-robopods/tree/master
Follow the instructions on the site, just add the line of code for the jar you want to include. Add the link under iOS section of your build.gradle located in your project directory.
Then just refresh Gradle. For eclipse, right click project, gradle>refresh all. You now have the jar in your Gradle Dependencies. Now you're just missing the code to show Admob ads and Google Play Game Services.
I have SDK (.jar file) written in Java. I created an Android Java Bindings Library following that description. I used the generated JNI files from the jar to write the API for my Xamarin plugin. I dont have experience with Xamarin, so I would like to ask you these questions:
My SDK.jar file depends on the Google Play Services.jar file. How and where I have to add it? I want to make the plugin to add the Google Play Services automatically to the project where it's installed my plugin. Like Google Play Services plugin adds Support library when it's added.
Could someone explain to me what's the difference between Components and Packages? I have these folders and I dont know in which one I have to add the Google Play Services Plugin and what's the difference.
How to get the current activity from my API files? I dont use Xamarin.Forms. Should I?
Thanks in advance
To clarify:
Answer for 2:
Components are Xamarin Components whereby packages are mostly nuget packages. User is not forced to publish component on Xamarin Component store, but many do. Some don't because Xamarin Component must have accompanying samples, documentation and screenshots, so for the large number of users effort to implement component is substantial. That is the reason a lot of authors just publish their SDKs on nuget.
Xamarin Components are tested before publishing by Xamarin Components Team and the reason is mainly correctness and quality (something like Apple's app submission process). This should help users to have minimal/starter samples that show how the SDK/component work and some documentation.
Some authors publish their components in steps: first nuget and when samples and docs are ready then Xamarin Component which references nuget dependencies mentioned in 1st step. This is called empty-shell (or just shell component). User can install it either as nuget or as component into some application or library.
Packages (nuget) are installed via Nuget Package Manager in Visual Studio or Xamarin studio. While components are added to you project. Samples and docs can be found in Components/ folder in solution root.
Plugins are special form of component used mostly for cross platform Xamarin.Forms (but not only) applications and they utilize special technique called bait-and-switch for loading platform specific dlls (from nugets).
Google Play Services (GPS) are not plugins, because they are Android only, so no need for plugin (ios and Windows parts). I think there is only Game Service on iOS, but not sure.
GPS come in 2 flavors as nuget packages and as components (empty shell).
Here are the answers of my 2 questions:
in component.yaml file before publishing the plugin: http://developer.xamarin.com/guides/cross-platform/advanced/submitting_components/components_and_nuget/
Don't have the answer yet...
Can't get it from API files if you dont send it as a parameter, but then your API is not compatible with the iOS API. Because of this I separated the plugin: one for Android and another for iOS.
Has anyone managed to extend "Mobile Backend Starter Java" on Android Studio
https://github.com/GoogleCloudPlatform/solutions-mobile-backend-starter-java
Frustratingly any documentation that exists seems out of date or only for Eclipse".
I want to use Gradle and not Maven , Android Studio and not Eclipse
I followed the Tutorial
https://developers.google.com/cloud/samples/mbs/
but the extend page left me confused
https://developers.google.com/cloud/samples/mbs/extend_backend
I would like to know if anyone has tried this
I thought about going from the other direction creating an app and then Google Cloud Tools and App Engine Backend with Google Cloud Messaging but I do not see a deploy , I did see this, Deploy Google App Engine backend from Android Studio
but have not tried yet
There is a project on GitHub which you can use as module. It provides you with the basic client libraries. You can use it as starting point. See https://github.com/thagikura/mobile-backend-starter-android-client-with-AndroidStudio and follow the instructions there.