Is anyone sticking with Google's new pay-for-play for Places SDK and Maps API access? Android Dev |
- Is anyone sticking with Google's new pay-for-play for Places SDK and Maps API access?
- Why kotlinx synthetic is no longer a recommended practice
- Latest Android Studio is slow as fuck
- Is there a way to contact a buyer from an order-id (from the order management tab in the dashboard)?
- Building Objects with Kotlin - CASTER.IO
- Face detection and tracking on Android using ML Kit — Part 1
- How can I align elements in list to elements in other items in the same ListView?
- How would you recreate the PlacePicker?
- Your Favorite way to Parse JSON in Kotlin
- Google's Permissions Declaration for reading SMS (UPDATE)
- I'm trying to develop an app that searches the web for different food recipes, does anyone know a good API I can use?
- Why are new AS projects created without the notification and action bar?
- Android at Scale Panel Discussion
- Understanding CPU and I/O bound for asynchronous operations
- BluetoothHelper - Android Bluetooth Library
- Where to learn about design/UX ?
- Android Studio 3.3 'Run' and 'Debug' trouble
- New, "Improved" Places SDK. PlacePicker deprecated! No more free Places autocomplete.
- " You cannot use AdMob at this time, Your AdSense account has been terminated." No emails, no warning. How do i fix this?
- Why does an APK get bigger after using R8?
- Checklist needed for phone reviews - features which are present/have gone absent in new models, and in Google Play
| Is anyone sticking with Google's new pay-for-play for Places SDK and Maps API access? Posted: 30 Jan 2019 09:16 AM PST I run a small business and have 200k+ api request a month places and maps access. In July when Google starts charging for Places access, it's going to run me $3,500+ a month. Is anyone moving to a cheaper service? Are you removing features? I am trying to come up with a plan of action for my mobile apps. Edit: Here is the email [I received.](https://imgur.com/a/MVkoBvY) [link] [comments]  | ||
| Why kotlinx synthetic is no longer a recommended practice Posted: 29 Jan 2019 11:18 PM PST https://android-review.googlesource.com/c/platform/frameworks/support/+/882241
[link] [comments]  | ||
| Latest Android Studio is slow as fuck Posted: 29 Jan 2019 11:04 PM PST Anyone with the same problem? Is it a memory issue? Build gradle: 3.3.0 Distribution url: gradle 4.10.1 When I load a project AS starts traversing my whole project tree ...one file after another...it interferes with what I'm doing and it's annoying as fuck....can that be turned off? [link] [comments]  | ||
| Is there a way to contact a buyer from an order-id (from the order management tab in the dashboard)? Posted: 30 Jan 2019 02:33 PM PST Hi, as stated in the title, I want to contact a buyer. This buyer (and he's not the only one) just bought all my games, but all of those are refunded soon after. Anyone knows how to contact a buyer? Or a trick to put in place in future... [link] [comments]  | ||
| Building Objects with Kotlin - CASTER.IO Posted: 30 Jan 2019 08:19 AM PST
 | ||
| Face detection and tracking on Android using ML Kit — Part 1 Posted: 30 Jan 2019 07:14 AM PST
 | ||
| How can I align elements in list to elements in other items in the same ListView? Posted: 30 Jan 2019 04:52 PM PST I am implementing a ListView with custom elements. The elements contain a Textview on the left site and another View on the right site. The TextView in the left can have different, but fixed sizes, while the right view has a minimum size, but is scalable in horizontal direction. I would like to have the right View at the same size for all elements of the ListView but they should be as large as possible. So the right View of all items in the list should start at the horizontal position, where the largest TextView in the list ends. Is there a convenient way to implement this behavior within the layout file? I don't know if it is possible to reference elements across the list items in the resources or of I have to code this behavior in java. [link] [comments]  | ||
| How would you recreate the PlacePicker? Posted: 30 Jan 2019 05:20 AM PST I have an app that allows users to check in and chat at Google Maps locations. I've been using the Google Places PlacePicker as the tool that allows them to select a place, with the intention of making a custom solution in the future. Google moved up my timeline by scheduling the PlacePicker for deprecation yesterday. I was disappointed, as it was the perfect utility for my purposes, but I understand the decision. I'll be getting to work today on replacing it with my own fragment. That said, I'm having a little difficulty figuring out what services to splice together to replace it. Here's what I've put together based on my understanding of what everything does: Place Search to get the user's location and put all places within the parameters as pins in a Map View, as well as list items in a RecyclerView, refreshing both views with another API call when user's location is changed or when the pin on the map is moved manually. An EditText with Place Autocomplete to replace the search bar on top for entering a location not in the immediate area. I can do without the "select this location" option above the list My app only needs the name and PlaceID of the place to work. Am I correct in thinking the utilities above would be the best way to clone the PlacePicker? Anything else I should consider with regard to cost and efficiency? [link] [comments]  | ||
| Your Favorite way to Parse JSON in Kotlin Posted: 30 Jan 2019 11:44 AM PST Ive been doing a lot of reading and there are a ton of different ways to parse JSON and make http requests so I have come to reddit to know what your favorite ways? [link] [comments]  | ||
| Google's Permissions Declaration for reading SMS (UPDATE) Posted: 30 Jan 2019 02:52 PM PST Original post: https://www.reddit.com/r/androiddev/comments/aahp6v/googles_permissions_declaration_for_reading_sms/ I re-submitted my form and still got a canned email saying I was denied.
As a result, I emailed their policy team explicitly and asked why it was denied. They still did not give me a direct answer or any alternate solutions, but instead, I received another canned email.
Not sure what else to do at this point. I might just have to give up on the app, and let it die slowly in the Play store. [link] [comments]  | ||
| Posted: 30 Jan 2019 02:36 PM PST | ||
| Why are new AS projects created without the notification and action bar? Posted: 30 Jan 2019 09:44 AM PST As of 3.4 when I create a new project with basic activity, the preview shows no notification and action bar, but when I emulate the apps they do appear. Any idea why the preview doesn't show them? [link] [comments]  | ||
| Android at Scale Panel Discussion Posted: 30 Jan 2019 03:02 AM PST
 | ||
| Understanding CPU and I/O bound for asynchronous operations Posted: 30 Jan 2019 04:10 AM PST
 | ||
| BluetoothHelper - Android Bluetooth Library Posted: 30 Jan 2019 07:14 AM PST I've created an easy-to-use library that lists the surrounding bluetooth device. If you have suggestions and comments, I'll take the time to develop for next versions. [link] [comments]  | ||
| Where to learn about design/UX ? Posted: 29 Jan 2019 11:02 PM PST So I'm looking into getting into android development as a hobby at home. I already know Java and I'm working in Java as a software engineer. I've played around with android studio building small apps to get used to it, but they all have the same issue: They look like crap! I can search a coding issue on stackoverflow and usually overcome all those difficulties but I can't search how to make my app look better. How does one learn about such things? [link] [comments]  | ||
| Android Studio 3.3 'Run' and 'Debug' trouble Posted: 30 Jan 2019 12:19 AM PST Ever since I upgraded to AS 3.3 I've had trouble with 'Run' and 'Debug' buttons. Pressing the 'Run' or 'Debug' button builds my project but does not open my app in the emulator when done. Probably due to the same problem, AS does not paus when hitting breakpoints. Is anyone experiencing the same problem? [link] [comments]  | ||
| New, "Improved" Places SDK. PlacePicker deprecated! No more free Places autocomplete. Posted: 29 Jan 2019 05:03 PM PST I just got an email detailing changes to the Places SDK. Of interest to me is that the PlacePicker is now deprecated, and will cease to function at all in 6 months. So the only free method of getting autocomplete for places is now going away. https://cloud.google.com/blog/products/maps-platform/introducing-new-improved-places-sdks I can only imagine that free use of the Geocoder is next on the chopping block for Android devs. That would be the final nail in the coffin for the app I've been working on for years. [link] [comments]  | ||
| Posted: 30 Jan 2019 02:33 AM PST | ||
| Why does an APK get bigger after using R8? Posted: 29 Jan 2019 07:03 PM PST
 | ||
| Posted: 29 Jan 2019 11:16 PM PST All too often we see that new Android devices arrive either without a feature that was present in earlier versions, or some new feature does not work any more. New users buy it with the expectation all previous issues will work - and focus on the Camera (as that has become the distinguishing difference between models). However, in practice, many phone models arrive with glaring omissions. Or bugs which are not remedied for months. What are the other features a review should cover - since it seems now not just new features, but earlier features also need to be benchmarked:
It seems that compared to print magazines of yesteryear, the new sources of reviews do not go into depth into all these issues anymore (except for a few review sites which focus on the camera and so on). There also should be a review of Google Play store for consumers:
Google Play store itself should have a What's New section to inform the public about upcoming changes - for users. If informing the public beforehand was a requirment, there will be less opportunity to sucker-punch the user with unexpected changes (like the Call/SMS changes above - which breaks tradition). [link] [comments]  |
| You are subscribed to email updates from Developing Android Apps. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment