Why Are Secondary Monitor Apps So Hard To Get Right? - Android General

Why are secondary monitor apps so hard to get right?
Hi Android enthusiasts,
I noticed that many of the secondary monitor apps in the Google Play store have terrible ratings. Reading the reviews, it seems that most of the issues are in device compatibility. The largest such app appears to be iDisplay which even promises connectivity over USB for working in coffee shops.
I'm wondering what it is that makes these apps so hard to get right. Is there some inherent technical difficulty that I'm missing? I read one suggestion that the variety of screen resolutions on Android tablets makes this difficult, but I can't see why this is a limitation.
The only reason I can seem might be vendor specific APIs that these apps have to interface with, but I can't see, from my experience, which these would be. It seems the harder bit would be writing drivers for Windows and OSX but that's really only one platform to support, unlike Android.
Another reason might be bandwidth, but surprisingly, this doesn't seem to be a big issue in the reviews.
What do you think? Shouldn't a good app like this be fairly simple to develop?

Related

Phone Programming Help

Firstly Mods sorry if this is the wrong section I didnt want to clog up the Development and Hacking forum. Please feel free to move this to the appropiate place.
......
I've got an idea for a little calculator app with specific functions which I know will go down very well with independent store owners. I've programmed a very crude prototype for Windows using my very very simplistic Visual Basic skills.
The problem is for this app to be useful I need it to run on peoples phones as a third party app so as its portable, and here's where the idea totally falls flat, with all the different platforms like Windows Mobile and Symbian i'm just wondering what would be the best platform to go for and if its possible to create a version that might work across a wide variety of different phones maybe using Java.
My ideal target audience will more than likely be Nokia, Samsung and Sony Ericsson users as opposed to Windows Mobile users.
Would it be just easier to commision different versions and how much should i expect to pay for a basic auto calculation app. I'm thinking of commercially selling the product is there any disadvantages of getting a third party to program the application?
All advice is appreciated and thanks in advance for any replies.
Well, I am not very familiar with the platforms you listed as preferred, but from what I know you will have to go with Java to accommodate them all.
It is still likely that you may need several versions if you want to properly accommodate the form factor of different phones.
There is no such thing as a best platform for a calculator app, which does not have specialized hardware requirements. Unless of course you are planning on a graphical interface so screen size or touch screen are major considerations.
If you really want someone to program for you for one time only, you may be interested in this site: www.rentacoder.com
As for price there are several considerations:
1) How much stuff does the app really do? How robust is it?
2) Are there other apps that preform same or similar functions and how much do they cost if at all? A quick search of the net may reveal that your idea has already been implemented as a freeware.
3) Will your software have a home? Basically when distributing commercial software you have to take in to consideration such things as registration, technical support for your customers and future updates.
Sites like www.pocketgear.com will let you easily distribute your app for as little as 5$, but many customers are unlikely to pay larger sums for an app that does not even have its own web site, let along a number you can call if you run in to trouble.
Thanks that was very helpful, i appreciate all the info.
Is there anybody with specific knowledge about programming for the other platforms?

Why are MOST windows apps so unaesthetically pleasing. (ugly)

Hello
This is not trying to insult anybody on this forum, but i would like to know,
Why it is that on Devices such as Iphone/Android, the apps look good, and are smooth, whereas on windowsmobile they often end up being ugly .
Obviously some are great on windows mobile, and run flawlessly,
however the majority of apps on the internet are unpleasing.
Take for example, towers of hanoi.
I know most will hate the game but oh well.
On the iphone, there are a few apps for towers of hanoi, this being an example
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now here is the best one available for windows, NOTING IT IS A PAID APP COSTING £6.84
millions of apps are like this, where there is not a satisfactory wm6 equivilant. this is only 1 app i came across in day to day life .
Saying that, most inventive games on iphone dont even have a wm6 equivilant, satisfactory or not.
Please note, i do realize millions of useful apps not available on other platforms are available on wm6, TF3D etc.
However to me ,I am getting annoyed with the lack of nice games for wm6.
Will this change when the windows marketplace is opened properly?
Maybe because WM is designed mainly to be practical? If anyone wants to see gorgeous landscapes simply copy photos of 'em to your phone and view them, on, for example a VGA screen which is incomparable to ****ty HVGA overiszed iPhones screen.
Want more games? Get yourself an emulator, for example SmartGear. It is paid, but (nearly) everything in iphone's app store is paid. After you get the emulator to work you get hundreds of games with excellent playability. But if you want inventions like:
a) pressing onscreen buttons and blowing into the mic to make sound
b) unlocking the screen by removing the simulated fog by your finger
c) game which is clever because its objective is to... press a button! yeah! The longer the better!
sorry, better get yourself an iPhone. If you managed to get this far and you don't want to kill me... wait for MS to designe the UI in a extra shiny finger friendly manner. Most likely developers will follow it.
I actually think a lot of the apps look nice; they could've been nicer, however, i'd prefer function over "form." Also, one of the reasons they don't look very aesthetically pleasing is becasue a lot are .NET applications so they're just there to deliver what the programs offers.
Because it's more difficult...
Because most apps are written by hobbyist programmers and we're forced to use standard .NET controls.
Programming fancy graphics is incredibly difficult and time consuming.
not that i know anything about applications,,
but having to use .net controls sounds pretty ****.
Its just annoying that android and iphone have applications so far ahead of wm.
I think wm6 needs a complete redesign.
Even wm7 shots look dissapointing.
One problem/strength of WM is that it is available running on a diverse range of hardware which is completely opposite to the i-will-ride-on-my-own-bicycle-only-:babycry: philosophy of iPhone. WM apps are designed keeping all these phones in mind, so to let the app get monetized to the max. iPhone apps have the same hardware, as there is only one iPhone, no choice. They have 3D acceleration, Fast processor etc etc on it, so they design graphics heavy apps that will surely run on their one and only target platform. If you have the money, have an iPhone, and play with the apps, if you dont, just f**k off, thats what apple's philosophy is. If you disagree, tell me an apple phone that comes for the price of HTC GENE.
Apps that are targeted for certain WM phones do run with all the iCandy as possible on that phone. I dont have any exact example right now, but i am sure somebody here will provide if needed.
For example, if an app is designed to run on a HTC Touch Pro 2 exclusively, i m sure you'll see much better interface than the one which is designed to run on as many devices as possible, from the low end HTC Gene to ultra high end TouchPro 2.
I hope this will clear things out a bit for everyone.
Just a few corrections of opinion
First off, whoever thinks that attaching some pretty graphics to the screen in .Net/C# is challenging, you seriously need to take more than an introductory class at a community college. It's not hard, you just have to be willing to find the graphics to use. Animation in WM is certainly more daunting and would be far easier to do if MS would have added WPF to the CF 3.5...
...the abundance of abbreviations in that last line just goes to show that programming is getting too annoying
Anyway, to answer one particular point which everybody else glossed over, is that Android ALSO has a lot of pretty apps like the iPhone (even though people ignore it). What people don't talk about is that android actually has it's own interface mechanism a lot like WPF/XAML which is supposed to be very friendly (I haven't really checked yet, but it seems to be popular).
A lot of people blame it on different devices having such different specs. While that SEEMS like a good argument, everybody who says it is blindly babbling without realizing that in 4-5 years the iPhone and Android phones will ALL BE VGA!!!!! If they aren't VGA, then NOBODY WILL BUY THEM!!!!! Hint hint, that means that both of those platforms will suffer the same problem that WM is "credited" with now.
The different resolution quality (VGA vs QVGA) is little more than a matter of releasing the original graphics in multiple sets. The issue of different resolution dimensions (WVGA vs VGA vs other-weird-boxy-GAs) could actually be handled (in most cases) with a simple bit of programming logic in the OnPaint handler.
Now, my answer to the question.....
Fact is, look at the programming communities of Android and iPhone, they both have a massive amount of open source/dev kit type samples, especially focusing heavily on graphics (especially with the iPhone, which focuses almost exclusively on graphics). WM samples tend to focus heavily on systems programming.
One other issue that exists is that interface programming is historically complicated with low-level programming languages. Apple gets by it using a highly customized and extended form of Objective-C. Android solves it with their xaml-like language which makes building the GUI a lot like writing a web page (loose comparison for the less technically inclined, don't flame me over the inaccuracies). Windows Mobile has the .Net framework, which can be made pretty without too much effort, but it suffers from not being fully integrated with the OS, therefore a lot of apps can be sluggish when written in .Net. The other option is to write in C++, which leads us back to the much more complicated UI programming.
There's your REAL reasons. Most programmers either don't have access to (or awareness of) good samples for a lot of the better graphics tricks, and the rest of them don't want to build something that runs too slow that it's going to get tons of complaints. I think there's one other contributing issue, there's not enough people who are willing to get together and partition out the work. It would only take 5-10 decently skilled graphics programmers to work with the high number of skilled systems programmers on this forum and we could see a nearly limitless number of high quality apps that would blow away anything on any of the competing phones.
As a side note, another thought strikes me....I think a LOT of people are waiting on the Tegra chips to start circulating before they start writing a lot. I know that's had me reluctant to put too much work into a few projects.
Because Apple has a bigger line of programmers.
Two aspects I can think of:
Apple has Steve Jobs, who happens to be educated BIG TIME in User Interface. iPhone is specifically designed (H/W and S/W locking together), so achieving it is easier.
WM (we're talking about WM, right?) is still based on PC / Desktop version, and the GUI (up to XP) doesn't change much. I believe 6.5 brings innovation (as I tested some cooked ROM) in smoothing the GUI. However, as an ex UIQ3 user, I believe, even if WM is intended for many devices (more standardized), MS can learn (and seems to be learning) from UIQ. All theme of UIQ changes a lot (scroll bar, text color, background). While for WM, the standard WM 6.1 theme won't even change the white background when we go to 'Setting' for example ..
Just my 2 cents coming from different world
After reading all this i still do not understand why WM apps, not games, are so ugly looking. People can skin various keyboards, Music Players, creat iPhone looking today screens, skin dial pads, calculators etc. Why not simple make the original app good looking? I'm not talking about animations either. Look how much better looking the dialers people are making compared to the standard dialer that some of our phones have like my Touch pro.
I saw someone on this site made a mobile version of Google Translator tool. Its perfect function wise but it could definitely look better. Someone on Ppcgeeks made a movie searching app called Cinemo. It's not ugly but its not as good looking as the Pre's Fandango app. I'm not talking about the Fandango apps function, just the form.
Look how well Weather Panel themes look & how good iContacts look. Why cant WM users have form & functionality?
charm1718 said:
After reading all this i still do not understand why WM apps, not games, are so ugly looking. People can skin various keyboards, Music Players, creat iPhone looking today screens, skin dial pads, calculators etc. Why not simple make the original app good looking? I'm not talking about animations either. Look how much better looking the dialers people are making compared to the standard dialer that some of our phones have like my Touch pro.
I saw someone on this site made a mobile version of Google Translator tool. Its perfect function wise but it could definitely look better. Someone on Ppcgeeks made a movie searching app called Cinemo. It's not ugly but its not as good looking as the Pre's Fandango app. I'm not talking about the Fandango apps function, just the form.
Look how well Weather Panel themes look & how good iContacts look. Why cant WM users have form & functionality?
Click to expand...
Click to collapse
Standardisation. There are no default "fancy" controls for either MFC or .NET for Windows Mobile like there are for iPhone (and I assume Android).
To make aesthetically pleasing applications for WM requires the programmer to design their own, making each and every application completely different in appearance. These small changes confuse & irrate most users as they can't find what they're looking for, therefore we just use the default controls instead of wasting time on making it pretty.
Secondly, putting graphics onto the screen is all well and good, but you want your app to run on as many resolutions as possible. That means resizing images (ugh) or having a separate image for each resolution making your application larger (ugh).
Blade0rz said:
Standardisation. There are no default "fancy" controls for either MFC or .NET for Windows Mobile like there are for iPhone (and I assume Android).
To make aesthetically pleasing applications for WM requires the programmer to design their own, making each and every application completely different in appearance. These small changes confuse & irrate most users as they can't find what they're looking for, therefore we just use the default controls instead of wasting time on making it pretty.
Secondly, putting graphics onto the screen is all well and good, but you want your app to run on as many resolutions as possible. That means resizing images (ugh) or having a separate image for each resolution making your application larger (ugh).
Click to expand...
Click to collapse
Are all programs skinnable?
I understand that making a program for various resolutions would be tedious but what I dont understand is why do people only make things look good after its seen elsewhwere? Nobody decided to make better looking media player skins until the iPhone came out. This also the same with contacts, dialers & keyboards. If this could have been done before, why wait until someone else does it then copy it?
When I look in Development & Hacking I see apps for specific resolutions. People post asking for different resolutions and someone else might make the changes if they have a device with that resolution. Is there something the developer has to do on his end to make an app skinnable or can they all be skinned?
charm1718 said:
Are all programs skinnable?
I understand that making a program for various resolutions would be tedious but what I dont understand is why do people only make things look good after its seen elsewhwere? Nobody decided to make better looking media player skins until the iPhone came out. This also the same with contacts, dialers & keyboards. If this could have been done before, why wait until someone else does it then copy it?
When I look in Development & Hacking I see apps for specific resolutions. People post asking for different resolutions and someone else might make the changes if they have a device with that resolution. Is there something the developer has to do on his end to make an app skinnable or can they all be skinned?
Click to expand...
Click to collapse
Skins have to be implemented by the developer. Although, all images that are used within a program have to be stored somewhere (either within the program itself or on your device) so those images can be found & replaced as many people on this board do. This does take some knowledge though.
And the reason people only came out with nice-looking interfaces after the iPhone is because it was innovative. It's a lot easier to copy an interface than it is to pick a design out of your brain & implement it from scratch
There's several reasons why WM has a lot of ugliness in its apps.
One is due to the UI itself. Non-fullscreen apps have both a top and bottom bar cluttering the screen and apps are rarely built to "match" the existing bars. The iPhone has less screen real estate taken up by the UI, so developers can control the look a bit more. Also, as I understand it, WM offers uglier barebones formatting. The iPhone gives devs access to prettier standard controls, menus, and fonts, whereas WM devs start with ugly and aliased controls and the like.
One reason is due to age -- WM has been around a (relatively) long time and many of the apps you're seeing were designed for devices with weaker visual capabilities and were also designed when the mobile app market was smaller and less competitive, so there was less incentive to make things pretty.
Another reason is due to the fact that a lot of WM apps are made by very amateur developers who simply don't have the training and know-how to pretty things up. WM, as a platform, seems most popular amongst IT workers, geeks, and tweakers. This is why there's tons of powerful, functional apps out there -- but a lot of us geeks don't know much about design. I, unfortunately, know about design but not programming.
I really didn't know who and what to quote, too many thoughts, so I'm just kinda re-reading the page and commenting back as I go. Sorry it's super long
charm1718 said:
Someone on Ppcgeeks made a movie searching app called Cinemo. It's not ugly but its not as good looking as the Pre's Fandango app. I'm not talking about the Fandango apps function, just the form.
Click to expand...
Click to collapse
You compare the Cinemo app made by a single unpaid developer against a corporately paid group of developers with pre-defined branding, graphics, and an advertising department (read: designers) under Fandango. That's a bit unfair
Ignoring function, most people on here could steal the graphics and duplicate the app's look.
Blade0rz said:
To make aesthetically pleasing applications for WM requires the programmer to design their own, making each and every application completely different in appearance. These small changes confuse & irrate most users as they can't find what they're looking for, therefore we just use the default controls instead of wasting time on making it pretty.
Click to expand...
Click to collapse
This is untrue. This is a now ancient viewpoint that's still held from the days of windows 3.x when everybody was tired and confused by the wildly bad interfaces that existed for business apps which took weeks and months to learn basic function. Sure, people want to have SOME consistency with their apps like how to close it or how to find menus, but an easy interface doesn't need to use only basic controls. If this were true, then each of the new mobile os's that come out would have failed since none of their interfaces match the other phones before them. The best designs offer more graphics than text, a more interactive and direct way of achieving tasks, and having as many options without cluttering the screen or adding more taps.
charm1718 said:
...what I dont understand is why do people only make things look good after its seen elsewhwere? Nobody decided to make better looking media player skins until the iPhone came out. This also the same with contacts, dialers & keyboards. If this could have been done before, why wait until someone else does it then copy it?
Click to expand...
Click to collapse
Also untrue. Sure, the amount of skinning went way up after the iPhone, there's been skinning on the media player for years. There's also been 3rd party apps that are far more attractive and functional for contacts and keyboards. The reason most people didn't see this is that these were usually paid apps or poorly advertised amidst hundreds of garbage apps on various repositories of shareware trash that people posted for WinMo.
typo said:
One is due to the UI itself. Non-fullscreen apps have both a top and bottom bar cluttering the screen and apps are rarely built to "match" the existing bars. The iPhone has less screen real estate taken up by the UI, so developers can control the look a bit more. Also, as I understand it, WM offers uglier barebones formatting. The iPhone gives devs access to prettier standard controls, menus, and fonts, whereas WM devs start with ugly and aliased controls and the like
Click to expand...
Click to collapse
WinMo developers can hide the top and bottom bars fairly easily (especially in .Net), so screen real estate is still available. I think many times we don't because we don't want to take away the legitimate use of those bars. As to the rest of what you said, spot on...the controls are ugly as opposed to the prettier ones built into other OS's. But remember what it was like to move from windows 98 (or 2000) to XP, the same thing will happen as winmo updates it's own UI libraries.
typo said:
Another reason is due to the fact that a lot of WM apps are made by very amateur developers who simply don't have the training and know-how to pretty things up. WM, as a platform, seems most popular amongst IT workers, geeks, and tweakers. This is why there's tons of powerful, functional apps out there -- but a lot of us geeks don't know much about design. I, unfortunately, know about design but not programming.
Click to expand...
Click to collapse
Very true, since the educated among us were never given serious classes on UI Design or Graphics Programming. The amateurs are stumbling through even a lot of the functional stuff. The hackers are usually good at changing something, but they can't create something new.
You also say something that brings up a subject I've complained about before (and is part of an argument I've made MANY times that we need a full-scale section just for development/programming instead of the single D&H sub-section we have now). There's a lot of people on here that are good at the functional programming. There's also a few (far less) who are good at the graphics programming. There's also a ton of people who are very good at graphic design and photoshop. A LOT of the apps that are released on here have terrible UI's because the people with functional knowledge don't take/have the time to make it pretty while at the same time those with graphic programming skill are wasting weeks trying to make their program functional while it's got a great UI already done. The two types need to work together and we could easily dominate anything ever done for any mobile OS out there.
btw, I want to add my own personal complaint. One of the most performant and potentially best looking API's belongs to OpenGL ES, which is a 3d rendering functionality all of our phones have built into the recent MSM chipsets. The problem is, only some phones have working drivers, and even less have efficient drivers. I would love to use OpenGL ES to write half of the stuff I want to, but I can't do that with any expectation of it being able to run decently on any phone older than the Diamond...and that's just among HTC phones...There's no certainty of any other handset having proper function or speed. This, to me, is one of the biggest setbacks and prevents a lot of devs from aiming high.
Thank you for clearing some things up. It would be great if the programmers and graphic designers could work together on more projects.
charm1718 said:
Thank you for clearing some things up. It would be great if the programmers and graphic designers could work together on more projects.
Click to expand...
Click to collapse
I'd like to get all three working together on projects. There's a few people who really know how to build the UI code, and there's a few wildly talented people who can put together graphics.
The thing I'd really like to do is get an organized team of people set up to work on projects, similar to how it would be done in any professional shop. A few guys who know systems/db/back-end coding, a few UI experts, and a few graphic designers. Baring that, at least get a list of people who would offer to join in on projects as they were put together.
speed_pour said:
I'd like to get all three working together on projects. There's a few people who really know how to build the UI code, and there's a few wildly talented people who can put together graphics.
The thing I'd really like to do is get an organized team of people set up to work on projects, similar to how it would be done in any professional shop. A few guys who know systems/db/back-end coding, a few UI experts, and a few graphic designers. Baring that, at least get a list of people who would offer to join in on projects as they were put together.
Click to expand...
Click to collapse
Have you reached out to anyone & tried putting something like this together?
charm1718 said:
Have you reached out to anyone & tried putting something like this together?
Click to expand...
Click to collapse
I've suggested it once before. For reasons that are too varied to get into right now, I expect that it would run into some complications on this forum.
With my current constraints (lack of gainful employment), I'm reluctant to get too deeply involved in organizing such a project unless it had the potential of turning profits. I do see a lot of potential in forming a group that produced both freeware/open source apps along with some commercial apps...I would be happy to be involved in that venture. If any serious developers are interested in a project like this, I would certainly find the time to organize and also be a developer.

Would Unity be the best for myself? Or another route?

Hello,
I've been doing some research on the many, many different routes I can go with Android development, and I'm hoping someone might be able to help narrow down my choice. My experience is currently web related, PHP/HTML/CSS, with knowledge of intermediate Javascript, etc.
I'd like to create a very similar game to Football Manager, but less ambitious. For those that aren't aware, it's a simulation game where you're the manager of a soccer team.
My ambition is to keep it very simple, dumbed down. No need to watch the games, pretty much all text with simple graphics for some things.
My issue is, trying to find a place to start. There's literally a lot of different routes, and I'm overwhelmed. Do I use HTML5? Java? One of the programs like Unity, Construct? PhoneGap?
For my specific game, and idea, what would be your best suggestion on what to use?
Thanks in advance.
you can try CocoonJS. it's easy.
It's html5 fraemwork.
CocoonJS is a technology that helps HTML5 developers publish their web-based games and apps in the most important mobile and web stores with no code changes and with all the advantages of native development.
Using CocoonJS, a single code base is enough to publish a game or app natively on more than 10 stores. Best of all, with no installations thanks to our cloud-based platform.
HTML5 is finally ready for cross-platform app and game development!
Learn more: http://ludei.com
But now it's in open beta.
All free, but all Extension only for premium users.
Premium account granted for free, if you have nice idia/project.
The answer is "it depends"
A couple of questions...
1. Will it only be for Android? or are you also planning to push it to iPhone?
2. Will the interface be more like a app (eg. gmail, calendar, utility apps) or more like a game (immersive, completely different interface) ?
3. Will there be a lot of interaction? or mainly consuming information?
pyko said:
The answer is "it depends"
A couple of questions...
1. Will it only be for Android? or are you also planning to push it to iPhone?
2. Will the interface be more like a app (eg. gmail, calendar, utility apps) or more like a game (immersive, completely different interface) ?
3. Will there be a lot of interaction? or mainly consuming information?
Click to expand...
Click to collapse
1. Android to start, possibility of iPhone in the future.
2. Straight forward, more like an app, nothing too pretty, more statistical.
3. Mainly consuming information, lots of behind the scenes work.
In that case, I would say go for a mobile friendly web-based app, as opposed to a native app. So this would mean HTML/CSS/JavaScript.
Reasons are:
You want to eventually be on both Android and iPhone. Since you're app is more "app like" if you go native, you'll essentially have to write 2 separate apps to have good user experience (Android and iPhone have vastly different experience guidelines). WIth a mobile-friendly website, you'll satisfy both with one code base
You've already got experience in HTML/CSS/Javascript - definitely a big win!
Since your app will mainly be information consumption, it sounds suitable for a website.
When done correctly, a mobile-friendly website can still be a great experience to use
A couple of things to be aware of...
Don't try and imitate the native UI on the mobile-friendly website. It is a website, not a native app! Users are fine if it doesn't behave like a native app (afterall, they would've just reached your site via the browser). In fact, if you make the website behave sorta like a native app, it might confuse users more. Best direction is to have a good, solid ,easy to use and understand UI. (Be wary of the Uncanny Valley)
Unlike laptops/desktops, mobiles generally are less powerful, so you'll need/want to optimise performance. Make sure the website runs fast & smoothly (ie. optimise resource downloading, minimise/optimise javascript animations etc). Be aware that most phones have a 'click delay' (to detect swipes/drags etc) so you'll want to use something like fastclick to eliminate this.
Remember that on a mobile device your user will be using their fingers (and not a mouse) to click/interact with your website. So make sure tap targets are nice and large.
Finally .... test on a real device! Chrome dev tools etc to simulate phone screens is great for dev, but actually using your website on a mobile will reveal many design decisions that might need to change.
This might sound like a lot to think about, but I think given what you've said about your idea, in the long run, it will be more time efficient. (there is probably a equally long list of things to think about when developing a native app!)
Good luck with your idea
pyko said:
In that case, I would say go for a mobile friendly web-based app, as opposed to a native app. So this would mean HTML/CSS/JavaScript.
Reasons are:
You want to eventually be on both Android and iPhone. Since you're app is more "app like" if you go native, you'll essentially have to write 2 separate apps to have good user experience (Android and iPhone have vastly different experience guidelines). WIth a mobile-friendly website, you'll satisfy both with one code base
You've already got experience in HTML/CSS/Javascript - definitely a big win!
Since your app will mainly be information consumption, it sounds suitable for a website.
When done correctly, a mobile-friendly website can still be a great experience to use
A couple of things to be aware of...
Don't try and imitate the native UI on the mobile-friendly website. It is a website, not a native app! Users are fine if it doesn't behave like a native app (afterall, they would've just reached your site via the browser). In fact, if you make the website behave sorta like a native app, it might confuse users more. Best direction is to have a good, solid ,easy to use and understand UI. (Be wary of the Uncanny Valley)
Unlike laptops/desktops, mobiles generally are less powerful, so you'll need/want to optimise performance. Make sure the website runs fast & smoothly (ie. optimise resource downloading, minimise/optimise javascript animations etc). Be aware that most phones have a 'click delay' (to detect swipes/drags etc) so you'll want to use something like fastclick to eliminate this.
Remember that on a mobile device your user will be using their fingers (and not a mouse) to click/interact with your website. So make sure tap targets are nice and large.
Finally .... test on a real device! Chrome dev tools etc to simulate phone screens is great for dev, but actually using your website on a mobile will reveal many design decisions that might need to change.
This might sound like a lot to think about, but I think given what you've said about your idea, in the long run, it will be more time efficient. (there is probably a equally long list of things to think about when developing a native app!)
Good luck with your idea
Click to expand...
Click to collapse
Thank you very much for your help, I appreciate all the information. One last question on my end.
I'm assuming the development tools would be the same as a usual website (ie. In my case, Dreamweaver?). If you're familiar with Game Dev Tycoon, would a layout /similar style of interaction game b, e capable using only Dreamweaver, or is something else needed?
No worries, more than happy to help
I would actually suggest not using Dreamweaver as for the mobile website, you'll really want to be as lean and minimal as possible. From what I recall, Dreamweaver can add quite a bit of 'cruft' to your code.
I would suggest a standard text editor (recommend: http://www.sublimetext.com/) as that would allow you to have complete control over your code, what you include/exclude, what goes where etc. The mobile site will require that extra attention as you really want to make sure it runs smoothly on the mobile.
In terms of quick dev iteration (making sure the site looks correct) you can use the chrome developer tools (https://developers.google.com/chrome-developer-tools/) which allows you to fake the user agent/screen size etc on your browser. Though nothing beats occasional testing on a real device - just to make sure you're on the right track.
Had a look at Game Dev Tycoon and I would say for something as involved as that (lots of interaction, animations etc) it's better to go down the native route.
pyko said:
No worries, more than happy to help
I would actually suggest not using Dreamweaver as for the mobile website, you'll really want to be as lean and minimal as possible. From what I recall, Dreamweaver can add quite a bit of 'cruft' to your code.
I would suggest a standard text editor (recommend: http://www.sublimetext.com/) as that would allow you to have complete control over your code, what you include/exclude, what goes where etc. The mobile site will require that extra attention as you really want to make sure it runs smoothly on the mobile.
In terms of quick dev iteration (making sure the site looks correct) you can use the chrome developer tools (https://developers.google.com/chrome-developer-tools/) which allows you to fake the user agent/screen size etc on your browser. Though nothing beats occasional testing on a real device - just to make sure you're on the right track.
Had a look at Game Dev Tycoon and I would say for something as involved as that (lots of interaction, animations etc) it's better to go down the native route.
Click to expand...
Click to collapse
Thank you again. I appreciate all your help.

[Q] List of Android Applications with Issues (power drain, leaks etc etc)

Hi again,
Bit of another weird question but i'm looking up applications that have issues such as memory leaks, Power drain Issues and a like. TBH, any application there is out there from sat nav to gaming, From simple notepads to full office suites. Everything and anything basically. Wanting to make a comprehensive list so that when we get our 'reports' sent to us it will flag up the particular application the customer is using that may be a issue. Even ones that have issues with certain versions of android.
Again, Thanks for any help
Ok then, Let me rephrase the question,
What applicatiuons do people know about that cause issues. From malware like GluMobi to Memory leaks of mGlow or Resource Hogs like hotmail to network hogs like netflix. Security issues like the one in apache cordova 3.5 and below to simple storage eaters like The SIms Freeplay.
ANY issue, not matter how big or small basically that can cause ANY potential problem. Technically, Its going be a HUGE list
Bugs, Battery Drain, Issues with certain versions of Android, battery drain, LITERALLY anything, No matter how big or small.
Thanks again
It's flat-out impossible to maintain an accurate list of what you're asking for. Most issues reported in most cases would be fixed within a few days as the apps get updated. Simply asking people to report these things is also a dangerous precedence and an ineffective way of doing it as there will be prejudice left and right, users reporting subjective information that isn't technically true and/or applicable to their specific phones and/or ROMs only. And how would you make comparison? How slow, leaky, disruptive etc does an app need to be to make it on the list? What if an app gets added that had real issues, gets fixed the day after, and then remains on your list for several more months because no new reports are coming in? It would be rather unfair to the developer(s).
Any truly disruptive apps are eventually removed and banned from ALL app repositories as the app host gets complaints about it (like Google bans apps from Play Store), so there's no reason to make a list of them here.
If i misunderstand your intentions with this list, i'm sorry. But you have more explaining to do before this idea makes any sense.
RobbyRobbb said:
It's flat-out impossible to maintain an accurate list of what you're asking for. Most issues reported in most cases would be fixed within a few days as the apps get updated. Simply asking people to report these things is also a dangerous precedence and an ineffective way of doing it as there will be prejudice left and right, users reporting subjective information that isn't technically true and/or applicable to their specific phones and/or ROMs only. And how would you make comparison? How slow, leaky, disruptive etc does an app need to be to make it on the list? What if an app gets added that had real issues, gets fixed the day after, and then remains on your list for several more months because no new reports are coming in? It would be rather unfair to the developer(s).
Any truly disruptive apps are eventually removed and banned from ALL app repositories as the app host gets complaints about it (like Google bans apps from Play Store), so there's no reason to make a list of them here.
If i misunderstand your intentions with this list, i'm sorry. But you have more explaining to do before this idea makes any sense.
Click to expand...
Click to collapse
Im in total agreement with what you say and this is just an extra feature that we are adding to what we already have. I work for a company in the UK and our intentions with this is we already have a system that checks clients hardware/software for what it has as we do a lot of work for many other big companies in the uk (all of them basically) as we have some very good engineers here. THe idea behind this database is just to flag certain things that may be causing issues and its more for internally than anything external although that as come up in meetings about adding this feature to the program we plan to release in the near future where 'certain' clients will be able to access our databases with our app we provide them. This is all preliminary at the moment and as i say, For our internal use only. This is why im looking for such a vast catalogue of problems, whether rumour or not
is not an issue at present. I'm just building the bare bone of this to test out how it works against our other databases and how easy/effective it will be working with what we already have.
Thanks for your answer and that's the conclusion we were at also. The fact that pre bundled software as total access to all information is kind of worring which we have dug up. This allows other programs that can get access to any of that information if it can pull a request from said bundled software. Example would be a program that requests use from the bundled program to read a PDF file (with the bundled software been a PDF reader). This is given access and then allows all the privileges of the bundled software. This is very very dangerous and a concern as most phone companies chuck plenty of bundled software (often not wanted by the consumer) on to there phones.
I was working on the 2G,3G,4G radios on all major phones the other week so im accustomed to A LOT of data entry
Thanks for your help my friend, Its good to know what we thought would be true but we have dug up a few other issues by doing this, So its not all a loss
EDIT: A piece of software still available and apparently malware/spyware is droiddream (bicchali.harish.droiddream) from what i can find on it. Also, Livelocker (net.livelocker) looks as if its got malware/spyware. As you say, What defines spyware is different in different peoples opinions but me personally am dubious about everything, As i think everyone should be but they are not. People just don't care as long as they have their facebook and crap lol. Point of interest about facebook, Funded to the tune of 12.8 Million by In-Q-Tel to get going, WHich was formed by the CIA. Just a little nugget there
I'm surprised no one as ANYTHING to say on the matter, Even if it's just on a whim that they hate app for x, y,& z. I have plenty personally lol

Apps to build apps

What apps are available to create Android apps on a Android device?
Call me crazy, but I think people make computer apps , software and programs with computers don't they?
Android is so open source, so flexible, so unstoppable. Why aren't people jumping all over this concept. My Nvidia Shield tablet has the hardware of a gaming PC of the 2012 era, maybe even better . Why I can't find anything about new wireless app creation with android devices is crazy. IDE's are cool but just don't complete the concept. And it's obvious that there's devices out there that clearly have the hardware and most likely the potential for doing so. Anyone care to partner up and make this happen for real?? It would quite possibly be the new Facebook or YouTube or Google in my opinion and definitely a great idea if not..

Categories

Resources