Hi There!
My wife, a doctor who is still studying, is wondering if there is a way she can use her new android phone to take better quality notes at lectures. Previously she was using a WM65 with Word, and taking text notes, but it was not possible or very difficult to add diagrams, or highlight important words, or draw arrows to particular things. Is there a great quality app that handles taking notes easier? Happy to pay.
Secondly, she has a forerunner watch which won't download her running data such as the track she ran, average speed, etc. Can she use her phone for that data collection and find a nice app to transfer it to her PC to view in a usable format?
We are also lastly looking for a cross platform (Windows 7, Android) shopping list application. Happy to pay, but would prefer one off cost. Needs to be simple and able to be shared across 3 devices nicely.
I think Evernote could do the first and last thing, taking notes, with schemes (maybe, not sure) and make a shopping list, which is cross platform, since you make an account on Evernote's site, and you have the Windows' program and the Android application to keep track, and it's off cost up to a certain storage
Hope I've been of help, just look for Evernote on google!
Hope someone can help me out. I'm looking for a note database to replace PhatNotes, since they don't seem to be making any progress on porting their product to Android.
So far I have identified Note Everything and Evernote as the two most likely candidates. But neither of them entirely fulfills my need. I want something that has a desktop (PC) version, but also syncs to my phone.
Evernote has the desktop feature, but requires an online account for which they charge after 'x' amount of space. That doesn't work for me, since I already have a SugarSynch account. I shouldn't have to pay extra to get access to my data. I also don't like the idea that my notes are in someone else's hands... it's a "privacy thing" for me.
Note Everything is a standalone product, but has no desktop component.
I'm hoping that someone will tell me that the file format for Evernote is the same between desktop and phone, in which case I can avoid having to pay twice to access my data.
Anyone have thoughts on this?
If you're looking at Evernote, look at Springpad. It has a VERY nice web interface and the Android interface is quite good and pretty similar to the web interface.
Boy, it'd really help if people would read posts thoroughly.
Hello everyone! I am new to the forum. Been thinking of joining for a while but my current issue has been the push I needed to join. I have looked high and low for the answer but to be completely honest I am not entirely sure what to look for. Not sure what my question is. I have also looked around this forum for a a good little while stopping on this thread to ask my question. I hope it's the right place to start. I will try to ask this in a way that is understandable and relevant. In your answer please take into consideration that I am new-ish to Android Development. =) (I can do the basics, Root, hack, crack, etc,.) I know enough though I think to follow your answerer and understand it.
** Question: For my Project should I go with a full Android App, go with a website that can be viewed on a mobile phone, or should I build the back-end on a web server and have an android app that delivers the front-end? (Front-end being the login, the styling of the pages, where the interaction between users take place, etc,. ) I'll elaborate on my question below. **
Alright. I started building a website. Conceptual anyway. I have been designing it on paper, white board, Photoshop etc,. The website is going to be a social site of sorts. Unique in it's own way. At first I was going to do just a website. Then I realized as my creation grew that I wanted it to be an App. Then decided, due to all the back-end server programming and functionality required, I would most likely have to build it as a website or web application. To give a brief summery of the site. There will be a login system with profiles, instant messaging. video chats, group chats, ability to play simple games like cards, chess, and more. I will also need to be able to control sessions. Write new session information on the fly based on certain actions the users take.
My problem, I think, is that i'm not sure the most efficient or effective way to go about doing this. If it was going to be on a computer I would write it up in PHP and obviously display the site with HTML/CSS. The display part I think is where I am at a loss. At least one of my issues. Since I would like for this to be an app for Android I may need a new way to display the 'site' if that's what It will even be called once it's an app. If I'm going to shoot for it to be on mobile phones then I'm thinking I can get the cosmetics looking good as well as using it to my advantage. I prefer the 'app-like-interface' rather than scroll with mouse and click on the page as if it were a website. ( 'app-like-interface': I am referring to buttons, and menus, and a overall 'pretty' interface. touch screen etc,.)
So should I write it as a website in it's entirety and just display it as a mobile site?
Should I completely trash the idea of doing this for mobile phones?
Should I (if it's possible) write everything on the back-end with PHP but create an app with java to display the styling and build the interface?
Or should I do something else entirely that I've not mentioned?
My apologies if this question was a bit to long. Tried to be thorough. Thanks so much in advance as well. This answer is something I need before I can even consider continuing. Thanks!
Az Tek
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.
I've been using Tasker for years now and it still is awesome. During this time I did a lot of automation with this but I never looked for alternatives and never checked whether I could achieve my goals in a simpler/faster/better way.
Now I know there are a lot of apps doing similar things:
Automagic
AutomateIt
Automate
IFTTT
and lots of other stuff I never heard of before.
I don't fear learning curves. It is not important for me that an app is easy to understand (it doesn't hurt either). I'd like it to be as powerful as possible and at least as powerful as Tasker. I would like to avoid sitting there for days trying to get where I am now with Tasker and then realize that I actually can't do some essential stuff.
I'd be glad for suggestions and opinions.
never pushed a thread on xda before...
"Put all your eggs in the same basket" as we say in France is not a good idea, but keeping one place to compile all recipes is also a good idea, from my standpoint because keep simple is always the best way to achieve big stuff.
So for instance: IFTTT/Zapier + Autoremote/Pushbullet > it rocks
But sometimes, when some stuff can't be done from IFTTT (tool too light for specific rss feed filter) or from Zapier (not free above 5 zap), I make the work from my phone directly with Tasker, all I use all plugins from Joao as I can (Autoremote, Autoinput, Autotools, etc..).
Since IFTTT or Zapier can talk to Autoremote, the possibilities to talk to outside and make the job done by other (appliance, cloud app, domotic box, nas disk, etc..) are endless.
well it turns out that 2gb ram is not enough by far. so i'd like to avoid having even more apps running in background. therefore i'm looking for one app to rule them all