Jump to content

Episode 235 with four apps you want to install right now right? and then vote cause that 's w...


G+_All About Android
 Share

Recommended Posts

Episode 235 with four apps you want to install right now... right? and then vote cause that's what we do here. :)

 

Appchecker (FREE)

https://play.google.com/store/apps/details?id=com.kroegerama.appchecker

 

Inkboard (FREE)

https://play.google.com/store/apps/details?id=com.inkboard.app

 

Xcerpt for Twitter (FREE)

https://play.google.com/store/apps/details?id=com.transcendentlabs.xcerpt

 

Make My Day (FREE)

https://play.google.com/store/apps/details?id=com.lonelyplanet.android.mmd

Link to comment
Share on other sites

1) Textra is, I am now informed, targeting Wear. What does that even mean?

 

2) Is it necessarily a Bad Thing that an app is targeting an old version? If the app doesn't particularly need anything from the new APIs is it still important to update - security or something? (I suppose the new app backup features would be useful for pretty much everything.)

Link to comment
Share on other sites

I'm torn.  I do think people should vote for an app based on the app itself, and not on the person who picked it.  But James is right, it's just fun to pick on poor Ron.  

 

Flo should totally troll us all one week and pick something like Google Docs as her app.  ;)

Link to comment
Share on other sites

Jason Howell Apps that "target" a platform are saying they can make use of a certain API level, right?  What difference does it make if AppX targets Kitkat if none of its features require anything higher? It'll run just fine on Lollipop or Marshmallow.

 

It seems to me that all AppChecker tells you is what APIs and capabilities an app CAN have... Not what it actually makes use of.

 

For many apps, there's no reason to target the latest platform. If they're rock solid and feature-rich while targeting KitKat, does it really matter that they don't say "Marshmallow"?  

 

I'm fairly sure a dev could just update the XML in his project to say "Target marshmallow" and change no actual code at all to be shown as "Marshmallow".

Link to comment
Share on other sites

James Ickes? Well, I guess my point is that not all apps need the extra functionally of the new targets. If they don't need the new features, it's perfectly reasonable that the app could be frequently updated and working perfectly with no need to target the newer platforms. Most devs don't have unlimited time or resources to make unnecessary updates, so the "why not" is that it's wasted effort.

Link to comment
Share on other sites

James Ickes I believe "updating" an app to target a newer platform is a simple XML change. By doing so, you don't have to actually implement any new APIs, so your app could show up as 'Marshmallow' but not actually implement any of the new features.

 

I've written a few small apps, and I always target the newest platform, but frankly none of them make use of anything beyond KK (since they're simple). 

 

Yes, if it doesn't target 'Marshmallow', then you know it can't have certain functionality granted by Marshamllow APIs, but that doesn't mean that any specific API is actually coded in. (Backup is mostly automatic, so you'd get that one, it seems.)

Link to comment
Share on other sites

 Share

×
×
  • Create New...