i have an Inspire4G, an iPhone, and an Atrix... i have unlocked and rooted and put Cyanogen & other mods on my Android based phones that I have now, and my N1 from the past as well as others for friends.
but i fully admit, i am NO expert... i rely on those who understand the system more than i, to do what i've done.
And, i am THANKFUL for all the work you have all put in.
SO - here's my issue, the iPhone has the group/threaded MMS ability... its a commonly known issue, a common question, and run through google shows many asking for options. some Blackberry devices can join these threads, and i'm pretty sure my iDen devices back in the day could as well. but Android cannot (currently).
i have tried GoSMS and Handscent, and it seems like they are merely better front-end clients with more/different notification features that feed off a base SMS/MMS from the core system. someone please correct me if i am wrong.
so - my questions: what keeps us from joining them? is it that an app can't be written to do this because the system can't do this?
is it simply that there is no way to modify the base Android system to handle this, and we all must wait for Google to include the needed code or libraries to do so?
is there not a... 'standard' or maybe available code from other systems that could be applied to the current base SMS/MMS system to allow for grouping in some way?
i ask today because the majority of the people in my world are iPhone users, and now that Group Messaging is active by default in iOS5, its becoming used more and more... to a frustrating level. i originally thought it would be as simple as waiting for GoSMS to thread the incoming texts, but as i've tried various options and apps it seems they're all based on something limiting.
and i'd like someone who knows more than i to explain (hopefully in simple terms) what keeps Android from adding what seems to be an old ability, really so i can know if there's hope for a change soon... or if its not even possible. hell, maybe this will come in ICS/4.0, or maybe its not possible.
again, thanks to all the devs - if it weren't for your skills and work, none of us would have the great devices we do.
Hello, first off I'd like to say I'm sorry if this is in the wrong section, but anyways, I'm trying to get things situated the way I like on my phone and I'm currently trying to figure out how best to achieve what I want while simultaneously having some fun learning and coding. In short my goal here is to combine my favorite aspects of AOSP roms and specifically the LiquidSmooth rom as that is currently one of my favorite AOSP roms I've tried on my s3. Also just fyi I'm currently running CleanRom right now because there are a couple features within touchwiz I'm having difficulty losing and as such I would like to start designing several modifications for a Rom.
The primary thing I really love within touchwiz is the lock screen. I like how I can swipe from anywhere on the screen to unlock my phone as well as the app shortcut mechanism, and while within cleanrom this has changed I also really liked how the sms and missed call notification was separate from the app shortcut bar in order to make it stand out. I'm also a really big fan of the swipe left and right for phone and messages within any samsung app that displays a contact or contact's thread (I wouldn't mind just having this within the people app but either way it'd be nice). There are also a couple motion actions I really like, particularly: direct call (call contact currently open in sms thread or contact card), smart alert (alerts you when you pick device up after a missed notification), and smart stay (attempts to detect if eyes are currently looking at the screen (this one I really just want more in depth look even if I can't incorporate it since it’s rather fascinating). And I also like the power saving profile that is within both the system settings and notification bar that is tied to an on/off switch instead of a change of actual profiles (just a preference here not really a necessity).
On the AOSP/liquidsmooth side of things the first thing is just the clean crisp and quick feel that AOSP roms seem to have (and no I’m not ruling out placebo effect but it does seem to feel less clogged). One of the main areas that I really love within Liquidsmooth is its notification bar. It is a very clean yet still attractive notification bar that is full of features (many AOSP but others that are more attributed to liquid). For example, something missing in CleanRom and potentially other touchwiz roms is the expanded notifications that include buttons such as reply, call etc. Though, one area in which I do prefer touchwiz is how they separate ongoing and notifications. Another thing that liquid has that I haven’t really seen elsewhere is the LTE toggle which I’d like to put in any and all roms I’m running just due to the battery drain caused by LTE radios (also wouldn’t mind adding longpress hidden menu to the toggle). Also I really like the quick reply function in liquid that shows a popup to quickly reply to text messages without leaving your current screen. Another area I feel Liquidsmooth really shines is its integration of settings into a sub menu within system settings because it just feels more natural and organized.
I’m listing all of these things because I’m trying to figure out how you guys would recommend approaching the rather large, for me at least, task here. Of note, while, I understand coding principles, debugging, style, the importance of commenting etc. I’m fairly new to setting up plans of attack on larger projects (my most recent project, designing an audio analyzer on fpga board using vhdl took several weeks to get anywhere major due to a difficulty of mine in finding where to start). That isn’t to say I don’t think I can do it, but I like to be as honest as possible so you know where I am personally. But yeah I would really appreciate any help or direction in achieving these goals. I know these things could probably be achieved by various hack job methods, but I’ve always preferred clean, from the ground up, complete and stable solutions but that by definitely doesn’t mean I’m against building off of previous work and improving the open source community. With all of that said what do you guys think? Should I start this project with a CleanRom base or a LiquidSmooth/AOSP base and modify them from there or start from a more blank slate and compile an entire Rom. Also, I really would like to start getting more and more into the android development scene as well as further my knowledge and skill base. I’m currently a computer engineering student with the intentions of heading into mobile computing either in operating system design or processor design though obviously the specific specialty could change a little though it will likely stay within mobile devices. I would consider myself generally proficient in C (and by corollary C++), VHDL and VB (cue VB flame comments ), but I would consider myself very good at learning new things and I have a very base understanding of other languages. Like I said my main goal with this post is guidance in how to start and in general go about accomplishing the above tasks. This is honestly one of my few forays into larger scale projects and my first android project, so any help, criticism, reference suggestions or advice is more than welcome.
Sorry for being so long winded but I’ve never been very good about keeping discussions about my favorite things short or to the point… especially when the topic is android… But I digress; Thank you those who read this and again sorry for the length…
I'm not a fan of Facebook per se. I don't care for the social media craze that seems to have permiated every facet of technology. When it comes down to it, I see Facebook as an enabler. It allows us insight into the intimate details of people we care about, without actually having to interact with them. It entices us to click "like" instead of personally conveying our appreciation or admiration. To top it off, I'm even less enthralled with Facebook on Android. Update after update that notoriously brings almost no improvement in performance, and many times results in an even worse experience. Not to mention the invasive permissions they keep slipping in with every new feature they implement. So why would I write an article about Facebook Home? Perhaps even more questionable, why in the world would I say they are "Winning"?
For most of us Android geeks/enthusiasts, there's been a quiet war going on behind the front lines of Android for quiet some time. Manufacturers continue to give us devices with their specific flavor of Android such as Samsung's TouchWiz and HTC's Sense, among other variations of Google's "Vanilla" Android experience. Meanwhile Android developers have been working endlessly to bring users more options with modified or custom ROMs such as Cyanogen Mod, AOKP, ParanoidAndroid to name a few. It's about choice - which the manufacturers don't want to give us. They want us to get used to their skins and their custom features, so that it becomes inherently habitual to use them. And we all know how hard it is to break habits.
Regardless of the ROM an Android user chooses, it doesn't end there. Android users are a unique bunch - and most of us want our phones to be unique as well. However, if you have been watching the evolution of the Android user closely (as Facebook undoubtedly has) you might have noticed that despite our yearning to be different, to customize our Android experience to our own taste, there is a sweeping movement taking place within the community: The Android user base has grown so quickly that it is no longer just a haven for the tech-geeks and device tinkerers. There is a large number of users that want to be able to customize their devices without having to learn what rooting is, or how to flash a custom ROM. They have no idea what a bootloader is, or even superuser for that matter. Yet their desire remains the same - to be able to tailor their phone as they see fit. This is where the ROM wars end - and the Launcher wars begin.
When it comes down to it, it doesn't matter if you're running Samsung's TouchWiz or the latest Cyanogen Mod Nightly. You're most likely going to install a custom launcher which will serve as your main user interface. Apex Launcher, Nova Launcher, or perhaps one of the new comers such as Chameleon Launcher or.. yep, you guessed it: Facebook Home.
This is where Facebook's genius begins to show. For the majority of Android users, it's not about what ROM you're running anymore (and for many newer users, it never was). It's the launcher that ultimately defines their device. And when you step back for a second and really dissect what's been going on with Android, it's always been about the launcher. TouchWiz and Sense are just that - launchers. Despite the fact they are deeply integrated with their respective phone's OS version, they're still basically just different user interfaces. Most of what they offer in regard to features can be successfully ported to other phones, other ROMs. The reason for Android user's past frustration with these manufacturer's customizations was their inability to remove them or change them. So where does that leave us today?
Facebook Home is exactly what a vast majority of the Android user base wants. Another option, another way for them to tailor their phone to their own usage habits. And if they don't like it, they can simply change their launcher or uninstall it completely. And let's be honest - there are millions of Android users who are Facebook fanatics. Facebook Home isn't just another app.. it's the new front line of the Android wars. Don't be surprised if you start seeing more of the major social media sites offering their own launcher. After all, it only makes "Sense".
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.
Hi guys,
Just curious, anyone uses REALTOR.ca app in Android here?
Because, here's the deal.... I'm actually the analyst for our app development and we're doing some major revamp to that app.
Now, a little disclaimer: the purpose of this thread is solely to discuss feedback on the app (I'm not a REALTOR(R) and will not be able to answer real estate questions), and my posts does not reflect my employer (Canadian Real Estate Association). This is a very non-official thread, so to speak.
A little background; we just rebuild our iPhone app into 2.0 and the feedback has been... lacklustre lol... Some thinks it's awesome, but others (most?) just want their old app back. Now, I personally want to engage the users more to avoid the pain with our Android app, but due to legal issues, business decisions, etc... I cannot create an "official feedback channel". So if you can somehow "forget" I'm an employee with CREA, please feel free to say what you think about the REALTOR.ca app.
Thanks folks
PS: What's in the works for now for Android 2.0
- Google Map (no more Bing Map) (this will solve all you KitKat users issue with the loading crap)(did I just say crap...? No I didn't...)
- Updated layout. More intuitive, side slides menu, better home screen, simplified filters (but advanced still there).
- Tablet support. Auto-detect device and display accordingly.
- New Near Me functions, new Open House functions, notes, notifications, etc...
- a bunch of bugs. Seriously, a lot of it. So much that we're thinking of releasing another update in the interim to address them.
PPS: If anyone in the real estate market and wants to know what I'm talking about, it's this: Play Store
PPPS: I don't think this app is "commercial", since it's free and stuff... but if I'm wrong, please feel free to delete this thread, mod. Thanks.