I'm making a party games which contains many games, so the size of the application may be "relatively big". So i was wondering the maximum size for a game not to have any problem, because i know some people who don't download any games above ~8-10mo. Are there many people like this?
That's why i'm looking for some figures about that. I looked on the dashboard of google, but there is nothing, and i don't know which kind of key words i can use on google for that (i tried some things, but i found nothing).
Thanks
Related
When in the iOS settings I activate the "Bold Text" in "General -> Accessibility", some texts get cropped because they become larger and thus exceed their intended display area.
Also, if I enlarge all the texts in "Accessibility -> Large Text", suddenly, my app becomes completely unusable because everything is cropped in all directions, the texts take a lot of space.
However, when I enable these settings and go to applications like TikTok, Wishbones, ... I notice that they don't seem to be affected by these system changes.
Having no time to set everything up now to make my application respond to these settings, I was wondering how those applications do to "ignore" those settings?
Preword
I think this is a valid question and I welcome questions like the above as that is partly how I got into accessibility (trying to work around an accessibility error instead of fixing it), but the below 'rant' will probably explain why you got the downvotes.
I also explain a way that you could fix your problem going forward in the section titled 'Proper use of allowFontScaling = false;' so I hope that is helpful to you / others.
Why should you never do as OP asked.
For anyone who stumbles across this question in the future, please read the following before doing the above.
I understand deadlines are deadlines and sometimes you need to push the product live, and if the above is purely to get your Minimal Viable Product to market as a short term fix then go for it, you have to be realistic about your goals and if accessibility wasn't on your radar until the last second then the fix may take too long, but make it priority before stage 2.
However, experience tells me that if you follow the example of TikTok, a company who deliberately suppresses disabled users videos, you have chosen a very bad role model. (I cannot comment on Wishbone as never seen it)
Now never mind the moral reasons of excluding people and disabling a feature they may require to use your App, instead let's talk numbers and lawsuits and see if we can't persuade you to add some time into the development budget to fix this.
Market Size
Globally, at least 2.2 billion people have a vision impairment or
blindness, of whom at least 1 billion have a vision impairment that
could have been prevented or has yet to be addressed.
Source: World Health Organisation (WHO)
With a world population of 7.8 Billion, that means that up to 28% of your user base could require larger text in order to see your App clearly. (The numbers seen high the WHO published but who am I to argue with them!)
If you are disabling font scaling the odds are you also haven't considered the size of tap targets, icons, screen readers etc. so your app is probably completely useless to someone who is blind or partially sighted, as well as people who have accuracy issues (tap target size, often influenced by font-size) such as people with Parkinson's Disease or Cerebral Palsy.
Excluding a quarter of the world's population does not seem like a good idea if you want an App to grow, unless of course you are building the next TikTok and have a good marketing budget to reach the other 75% of the population.
If this is the case then ignore accessibility, unless the law in your country leaves you open to a legal nightmare.....
Legal
Oh this one is going to be the biggest commercial reason to do this, large companies are getting battered by lawsuits in America where their websites aren't accessible, Apps are not going to be far behind.
Now I am not sure which country you are from, but depending on where you live you may actually find that your App is breaking the law.
I myself am from the UK and although the risk of a lawsuit is much lower here I am aware of at least two lawsuits being put together on behalf of people with disabilities against companies whose websites are inaccessible to blind people. We are following America and I have no doubt others will too.
Oh and legislation is in progress for the whole of Europe called the European Accessibility Act, so every EU country will have the same laws soon.
It isn't just people with disabilities.
I work on a 43" monitor positioned about a meter away. Now if Windows decided they would stop font-scaling I would have to completely change my setup as the font size would be too small and i would not be able to read anything.
I have no vision impairment, but the accessibility features built into Windows, web browsers, applications etc. really allow me to work the way I want to.
If I am on a train I often switch accessibility features on to make tap targets bigger so I can press them accurately when the train is buffeting around, contrast better (for glare from the sun so I can see the screen better) etc.
Tried the new 'dark theme' yet? Dark themes started for people who have issues with screen brightness and contrast perception problems. See that thing in front of you that you write on, typewriters / keyboards were invented for blind people and I cannot imagine a world without my keyboard.
Accessibility = a better experience for everyone = happier customers / users = better reviews and recommendations = more customers = more profits = more development work for us devs = everybody wins.
Proper use of allowFontScaling = false;
allowFontScaling = false; is a very useful thing to add to your toolbelt.
As OP has discovered sometimes a layout does not work when someone changes the font size in their system settings.
Obviously you should design your layout to accommodate larger text, but this will often ruin a pretty design if it hasn't been considered from the start.
Educating your design team takes time so it is often left to us as developers to fix these problems until company policy changes (which is easy to do if you point out the legal implications, directors tend to wake up when you mention multi-million pound lawsuits and a larger audience!)
Instead if you encounter the same problem as OP and there is no way to fix your layout you could do the following and still comply with WCAG 2.1 and offer your users a feature they may require to comfortably use your App / Website.
Disable automatic font scaling as suggested in the answer given.
Add an accessibility settings section to your App / Website.
Add an option to control font size, font weight etc. there
If the font size / weight is adjusted to a size that does not work with your 'default' layout, enable a secondary layout that will accommodate this font size / weight. Allow up to 200% font scaling in this secondary layout (it can actually be quite fun trying to accommodate such large fonts on a small screen - requires some creativity!)
While the secondary layout may not be as nice it does at least mean that people can use your Website / App if they require a larger font size / heavier font weight. It increases your potential customer base and helps you comply with relevant laws.
Conclusion
Put accessibility on your roadmap today.
If you build into your design process you won't have to resort to terrible ideas like disabling font scaling, ignoring accessibility errors etc. It will also save you a lot of effort later trying to reverse-engineer your App / Website in order to accommodate features that people need.
If you are near the end of development like OP, add it to your development plans as a priority item going forward to increase the number of potential users of your App and to avoid legal issues.
/End Rant
I hope it helps at least one person see the benefits of accessibility.
One thing you can do is to disable font scaling for Text like below which will make sure that your font size is not affected by Accessibility changes.
Text.defaultProps = Text.defaultProps || {};
Text.defaultProps.allowFontScaling = false;
I am interested in getting into user interaction/shape detection with a simple usb webcam. I can use multiple webcams, but don't want to be restricted to using something like the kinect sensor. My detection cameras need to be set up on either side of a helmet (or if an individual one, on top). I have found some, but they don't really have the functionality I need and most are angled towards facial recognition. I need to be able to detect a basic human skeletal structure and determine if something is obstructing it. I would really rather be able to do it without using any sort of marker system on the target person. I would like for it to be able to target multiple structures. Obviously I am willing to do tweaking if necessary, but want to see how close I can get to what I need before I rebuild the wheel. I am trying to design an ai system that can determine how many people are in an area and where they are.
Doubt there will be anything like this since Microsoft spent a ton of money on the R&D for Kinect and it's probably all locked behind an NDA. I'm also guessing there's a lot of hardware within the Kinect that is not available in a standard webcam.
The closest thing that I could find to what you're looking for is the OpenKinect project, might be a good place to start your research.
I've done some research and so far haven't found anything very helpful. My question is what technology can I use to identify at least most nude images, etc. when being upload from users to my site and not allow them to be posted? From what I understand, there isn't anything "perfect" of course but I would like to get a good start with something half decent verses nothing at all what-so-ever. Any suggestions, links, or helpful bits of information are greatly appreciated!
You could make a histogram of the images and check for the amount of skin-tone-ish pixels.
I would go the route of building your own.
Here is a good project that has helped me in my first attempts at image recognition
http://www.codeproject.com/KB/cs/BackPropagationNeuralNet.aspx
There has been a lot of success with writing tools that look for nude images. Generally speaking, they look for certain amounts of skin-tone and/or shapes. Those will flag potential images for human review.
good luck!
I want to develop a game which will have following content
1. User will log in
2. User will be provided by alphabets of a word falling from sky, and he would be required to complete the word before they hit the bottom level.
3. The words would be pulled up from a database.
4. The reward points gathered by user on completion of task, would be converted to a corresponding "Mobile recharge topup" and would be sent to users mobile.
I was planning to do this in a html5 using Canvas element. Could you let me know, if this is possible.
I have studied 5 mobile recharge api service, but none of them are satisfactory so far. Any direction in there?
To give you an idea of my expertise with this, I am a totally new user of web programming. I have been a systems programmer before, and need to develop this for assisting in a research project related to studying economic incentives of attracting low income workers to spend time on web, if enough incentive is provided.
I sincerely appreciate your time and help.
Thank you,
Mrunal
This is what I have found.
It is a half baked script ...
http://www.javascriptsource.com/games/falling-by-tim-withers-120409100502.html
in a few months I've got a game to play, but I want to cheat a bit :P by using some webcams.
The game is simple you drive with your car around and try to spot images that are taken of the roadside. But I was thinking if I use some webcams, I could scan the surrounding for these photos. I will probably still need to look for these photos but it helps me a lot.
I was thinking maybe I should use OpenCV with Feature Detection, but is this the smartest?
Better than the smartest, you should look for the stronger one.
Some times ago I've worked with opencv + SIFT which gives support for rototraslation of what you're looking for and can do progressive finding by adding feature to the checks.
It may be a good idea, and you can find opencv implementation here