List of apps people pay for but have low rating
ideasfilter.com
ideasfilter.com
So far checking only 3 marketplaces, my crawlers found so far about 100k apps, the default filters show only the more interesting once (paid and low rating)
Its free.
I will add more and more marketplaces eventually. I will also try to add some social features, like "working as a team on some idea" and posting own ideas, but will see how it goes.
Feedback welcome
EDIT: i just see it on mobile, it does not look ideal. Will need to work on that hm.
EDIT2: just added pagination :), hope it works for you.
I guess robots.txt is all that really matters.
Here’s Play Store’s: https://play.google.com/robots.txt
There is no reason for these companies to go after some small guy scraping the app store data. But who knows - Craigslist went after one man shops. These companies might too.
Not exactly - robots.txt will prevent Google from crawling the page but it might still show up in search results (without a snippet or your page title) based on how others link to it.
What consequences ? Breaking ToS can get your account suspended if you even need an account for doing this, not sure what else breaking the TOS really implies.
I don't know if Google can claim ownership of this data as it's customer generated and publically available.
https://law.justia.com/cases/federal/appellate-courts/ca9/17...
There is an attached PDF with the full decision, Pages 27, 28 on reference some related cases that informed the decision.
Is Apple’s iOS App Store “public” though? Ostensibly it’s only open to Apple customers with an iOS device: accessing App Store pages in a web-browser just redirects you to the App Store.
Not if you are on an non-Apple device. Or access an iOS App Store page from a Mac. The pages show just fine.
Can someone explain the value of such a list, am I missing something? Don't get me wrong, your project is neat and I enjoyed looking through it, but I don't understand how anyone would try to sell this or pay money for this.
Maybe these are apps with bad user interfaces or some other issue and it's a list of low hanging fruit ideas?
One app kept track of my car info (vin, insurance, mileage, fillups) and was useful. But one day it was sold - uploaded my data and put it behind a login.
P.S. Do you remember the name of that auto app? Name and shame! ;-)
Another app I had that got worse was camscanner - a scanner app that would take a picture of a document and create a .pdf out of it.
It was sold to tencent. The "privacy policy" - when you could access it (broken links) was written in broken english that basically said it did anything it wanted with your .pdf files.
The kinds of documents I would image to .pdf were extremely sensitive personal documents - think w2, documents with SSN, etc...
At least apple notes eventually added a version of camera to .pdf (though it wasn't obvious how to use it when it came out)
If anyone has good alternative suggestions I'm open, I haven't tried to look as I don't use it much anymore.
You can also do it natively now in iOS Files app and Android's Google Drive.
I dont think i will put on a pay wall, i will rather try to build a community.
So, sometimes market research is very valuable. This risk you have for "solving problems you personally have" is that you can end up trying to build infra tooling like new databases.
I agree! I didn't intent to discount market research.
>This risk you have for "solving problems you personally have" is that you can end up trying to build infra tooling like new databases.
...which is great and should be encouraged, if it's enjoyable! I was thinking more along the lines of an app store ratings scraper
Also, some might sell because their App resembles something popular so some users buy by mistake. Then make sure, it does not parasitise on your app!
The real business opportunity is the sale of the list of course. It’s sort of like selling shovels to and booze to gold diggers.
You can glean information about your competitors’ usage and advertising, which can help you optimize your own app’s advertising spend.
Q: How do you evaluate if the apps are still being paid for?
Like the "Automatic Call Recorder Pro" (highest number of ratings on the list) has "try the free version first to see if this will work on your phone" ... I feel sorry for Android developers. As much as I dislike the "Apple way" of designing products (walled gardens and super opinionated instead of open and providing choices), every time I need to develop something for Android I'm flabergasted at how shit the platform is under the hood. Soo many APIs to do the same thing, depricated system APIs all over the place, but the only way to do things on devices X, but only from manufacturer Y, on Z the API functionality isn't even supported, on W you need to use newer APIs, on Q you need to use a custom solution - nobody really uses Q but your client got 3 complaints and can't determine priorities (understandable given the ecosystem fragmentation)
Call recording used to be easy to implement, until Google took a look at the obvious security problem with apps recording calls from the background, and restricted the normal APIs to system software only. If an app has automatic call recording that works well, the manufacturer probably put an insecure OS on the phone, because then any app or game you download probably has that capability.
The supported APIs all have excellent backwards compatibility through AndroidX. You can still many if not most modern APIs all the way back to Android 5 without much change in the code. Most system APIs are backported through Google's libraries, and for many others the standard compat library has shims that avoid most version checks. This is sort of the opposite of iOS, where most users are updated within a few months so many years of backwards compatibility isn't a big priority.
Cheap, slow, crappy devices and background task killers are much more of a problem than the problems plaguing a lot of the APIs.
In these situations where recording is agreed by both parties, getting restricted on the individual side is frustrating.
Basically it's the proverbial technical solution to a social problem.
I remember it as a matter of consent and most resources point to it being OK as long we both parties are aware.
e.g. http://www.dmlp.org/legal-guide/recording-phone-calls-and-co...
1) Low demand 2) High impact of getting it wrong (untested legal consequences?) 3) lack of a good story. IE: why can't you track what was said in another method? Ie: paper note
Call recording is legal even in 2 party consent states... with consent. Also often legal if it's to protect against a major criminal threat.
> IE: why can't you track what was said in another method? Ie: paper note
Try convicting your attacker with that.
It turns out that Georgia is one of those states. You can tape a person without their consent, and broadcast it?
This sounds like a good story, but it's written in a way that I'm expected to fill in the background.
(d) (1) Subdivision (a) does not apply to the disclosure or distribution of a confidential communication pursuant to any of the following:
A party to a confidential communication recording the communication for the purpose of obtaining evidence reasonably believed to relate to the commission by another party to the communication of a crime as specified in Section 633.5.
https://leginfo.legislature.ca.gov/faces/codes_displayText.x...
What? Federally call recording is legal with single party consent. 35 states and DC have single party consent.
End of the day, 90% of phone recording use cases are bad ideas, and making it moderately more difficult to do avoids alot of trouble.
I once got a call from a person threatening my life. I find it hard to justify not being able to record such a thing because of some strange hypothetical scenario about bad actors recording calls.
To be honest I can’t think of any scenario where recording your own calls would be bad. Can you give me a example?
But, have you ever had a conversation on the phone that was difficult, not your best, or otherwise problematic? Have you ever said something that you would only say to one person?
The lower the barrier, the worse people’s behavior will manifest.
Why should the fact that the conversation is held with a phone change things?
The arguments only holds if you forbid all recording.
Reductio ad absudum.
Anyway, I used to rely on the call recording quite heavily, and I was really pissed off, when I discovered that it doesn't work anymore, so all my recent calls are lost. This was really awkward, because knowing my calls are recorded I stopped writing down appointments or ask to repeat something I didn't hear well, because I can just replay.
Without all that stuff there's really not much point using phone at all. Except most messengers and services require you having a phone number, which is absolutely ridiculous.
Assuming you port your number there, I've found Acrobits Softphone [0] to work exceptionally well; if the price tag is an issue, Android has built-in SIP software in the vanilla Android Calls app. Highly recommend their service, doubly so as it means I only need a data plan - meaning I only pay $15/month for calls, text, and (3GB) data, which is no mean feat in Canada!
[0] https://play.google.com/store/apps/details?id=cz.acrobits.so...
That might make it less useful for people in one-party states who want to record secretly, but it would be better than nothing.
[1] My first android phone would get physically disconnected from microphone input by the modem during a call
Just 6 months ago I took a small side project to port a web app to mobile and add some native functionality. I need to connect the user to a WiFi hotspot (industrial device controller) from code - the new APIs were absolutly not backwards compatible, the old APIs were just killed in Q, even worse the capabilites present in the old APIs (controlling WiFi networks) half wroked on older devices, depending on vendor (eg. not working on Samsung, working on a Pixel, etc.)
iOS didn't expose the level of controll straight up and I was able to explain to client that that's just not possible. We saw Android was all over the place in this regard, but because a competitor had a halfassed version that only worked on some devices the client insisted it was possible to implement this on Android. It took us a week to figure out that the whole thing is an unmanageable mess and demo to the client that the competitor is broken in so many scenarios and that we should just use the system UI like we do on the iOS.
>On iOS, these apps would probably not even be available.
See but I prefer this to Android "it's possible because we were wrong, now we leave it out there but you can't do it going forward". Why not just blacklist it in app store and prevent new apps from using it on review ? Also it's obvious they don't have any sort of certification testing for these APIs because they just straight out don't work on various vendors - they could easily mandate that to qualify for Google services on your device you need to implement system APIs and pass the test suite to solve these inconsistencies.
In theory the answer to this is for the app reviewers to scrutinize any app using those capabilities to make sure it's not abusing them, but in practice the app approval process is actually kind of crap and doesn't do a good job of making those distinctions.
Your remaining alternatives are to prohibit that thing from happening whatsoever, which pisses people off, or to make it possible but a huge miserable ordeal, which pisses people off.
Make the ability to use the network an app permission that can be denied.
Shady app records my call? Who cares? It can't send the data anywhere. (Assuming the permission is properly implemented.)
You are probably falling for the misdirection Google lay out for you. Its users are the advertisers, the licence buyers and data-consumers.
The person operating an android phone, getting navigatinal directions or performing a search is not their user. 'The product' as is being repeated.
The rest of it is a marketing expense.
I think that's a simplistic way to think of it, and assumes that there are only "apps" with exactly one privilege level. There are a multitude of things the OS could do to give a good user experience AND stay secure from random apps recording you.
Off the top of my head, how about: Apps can record you, but only by registering a special chunk of code that will be run with a special "tempfile" privilege, where the app doesn't know where the file is stored to. Then, once the call is over, if the app tries to access that file again, with normal privileges, the OS puts up a confirmation screen that says "Good news! App <Dave's Cool Pachinko Parlor> has recorded your last call. Do you want to keep or delete that recording?"
Now you might have a different opinion, that call recording is a basic feature that all phones should have. And I would agree. But if you have any such opinions then IOS is dead on arrival anyway.
If they didn't want these kinds of things they should implement app store policies on what APIs you're allowed to access.
I say this because I have seen excellent but popular apps have very low ratings just because they are popular. Also, when someone gives it a low rating because of a bug that’s fixed 2 days later, is there a mechanism to take that into account?
I also imagine that most people who'd buy civ on the app store are like me: looking for a more convenient way to play the game, already used to it on PC, and find the ipad offering quite dissatisfying.
Like if the AI isn't even playing.. that sucks.
You must read the review text and count what aspect each review is talking about. And then on analysing you will have an insight on what you should or should not change.
I haven't seen a difference yet, but I read for app store optimization purposes, higher ratings help.
Makes sense.
If you don't receive much written reviews but only low star ratings, it probably means that your app is asking the wrong users for a review or asking at a bad time.
Popular non-scam apps with low ratings probably simply fail at the feedback collection and communication with their users.
The issue seems to be (based on the negative reviews) that people don't understand the game. They assume it is like popular game X, but they're playing a different game.
The tutorial explains that the game has a view distance and fog of war.....but the top reviews are negative posts about opponents in the distance "disappearing"....
There are many other reasons why an app might have low reasons despite being pretty good - for example, people often have unrealistic expectations of technical apps, in spite of the fact the app does exactly what it's supposed to. So, many people give it a low review, but the few people who understand the limitations find it useful enough to pay for.
Both of these types of app will find their way on to this list, but there would be no point in trying to build a better version.
> when someone gives it a low rating because of a bug that’s fixed 2 days later, is there a mechanism to take that into account?
I think so on the play store. Not sure though.
The source and the credibility of the ratings is an important consideration.
Cool job though!
I can add it but some other improvements come first.
Or better yet, rather than more in the dropdown, just have two separate filters, one is rating and rating count, the other is ascending/descending sort.
>
> bugs or other issues
>
Other issues == not free.I have some experience running apps with 1M or more users.
In my experience, I see that 10% of bad reviews are due to bugs while 90% are because a user really needs the app/service, but it is not free.
Which also means this: if the application is useless (and just steals your data), then it will have good reviews.
Basically some free users when presented with “you need to upgrade to use this” will leave a bad review. And that is 100% logical: some users believe that all online software should be free. And they never pay for software at all (since their company or school pays, etc. - but they don’t).
1. Just because it's failed in the past doesn't mean it's going to fail in the future.
2. Context is utmost.
3. We need to stop assuming that people are stupid and start believing the complexity is okay sometimes. I believe a tyranny of the majority is no more helpful in software than it is in democracy, so I don't buy into Pereto. That one belongs on the trash sheep along with UML, Agile, and other systems and theories of software development. IMO, of course. But there's a time and place for complexity. Audience matters. I think I'm preaching to the choir here.
I've tended to write free software, designed to meet needs (as opposed to make money), but this is a good idea, and one that I think could be useful to folks that need to come up with "that big idea."
Turns out he noticed there was a really popular app for... the bible, but he noticed it was pretty shitty. IIRC, he then made his own without too much effort, published in the app store, and made a decent chunk of change off of it for quite a while.
https://www.producthunt.com/posts/ideas-filter
The link to PH is also on http://ideasfilter.com/ top right
Weird.
The is no domain alias for that address so far.
The trick is to of course read a few of the ratings to get behind the rating number. I also filtered for 1000+ ratings as who’d want to develop an app based on research for a app no one is using.
A theme I saw in my 5 minutes of usage were apps that were once loved and popular but have been poorly maintained through the android updates. I get that for small app devs - I had an app and I got so many “ya gotta do this” emails from Google I just abandoned it. It was a free app so didn’t feel so bad.
i think i rather build a community around if i can and find some other way to monetise this, but will see.
I think the pattern will be different for different platforms
It'd be very helpful!
Good job by the way!
and thx, peoples interest and praise is quite motivating
I also tried to add G2 as an another app market place but boy they really dont wish to be crawled so i need to pass on them.
It should be mentioned though that G2 reviews are usually pretty heavily positively manipulated via "Review for Amazon Gift card" schemes.
[0]: https://www.g2.com/
https://alternativeto.net/platform/online/?feature=software-...
love your project
UPDATE: It seems G2[2] has data about pricing.
[0] capterra.com [1] trustpilot.com [2] g2.com
Stackshare was great in the beginning, but as is the way with every site with crowdsourced reviews, business motives (incentivized/fake reviews) or personal motives (writing shallow reviews for "clout") took hold after 1-2 years (around the same time the added the signup popup).
Lets say we build a better version of stackshare. What would be the things you would look for, as a user (other than honest reviews)? It is near impossible to do a good job of comparing features, even having up-to-date pricing data is hard. So what else can be added to make it useful?
A few possible improvements over Stackshare:
- Honest & in-depth long-form reviews. Quality matters so much more than quantity. Even a single in-depth blog post every few weeks would provide more value than the crowdsourced ones you currently find on the site
- Openly accessible, and no social/gameification features that nobody needs
- Better categories and making it possible for a tool to be in multiple ones (and being able to see it). The structure of the current ones is a mess. E.g. CMake is in "Java Build Tools" but the "C/C++ build tools" category is basically empty with 2 tools.
- Better searching/filtering. Kind of connected to the previous point. They have the data (don't know of which quality) of "Tool1 works with Tool2", so you could possibly have a more generic "Build tools" category and then filter by "works with Python".
- I don't care much for automatic comparison features, as they often don't yield good results. E.g. Jira often looks good in such comparisions, but you'll still want to bang your head against a wall every time you have to wait for it to load one of it's pages. A good alternative would be a quick overview of key metrics and category-dependent badges, which you can use to form your own opinions. RubyToolbox[0] does a fairly good job of that.
All good ideas. Though keeping the reviews up-to-date might become a full time job in itself, as software changes often. I use a service called clickup, they add features constantly and quickly.
How does ruby toolbox do the categories? All other data they show can be automated, but I wonder how they do categorization. They probably use the topics feature from github, I still think it is hard to automate it fully.
Edit: Ah, never mind. Found this https://github.com/rubytoolbox/catalog