Sign In
Register
Help
Post your comments for Jobs for iPhone here
Page 1 of 1
Jobs for iPhone
MultiQuote
#3
macFanDave 
- Member
-
- Group: Members
- Posts: 777
- Joined: 04-March 04
Posted 11 March 2009 - 08:14 AM
I don't see how the App Store allowed that title to get through! It's going to lead to a lot of confusion -- I thought I was going to be reading some of Steve Jobs' thought on the iPhone.
#5
macFanDave
- Member
-
- Group: Members
- Posts: 777
- Joined: 04-March 04
Posted 11 March 2009 - 02:14 PM
bcode said:
Well... Employment opportunities have been around much longer than Steve; Hard to put a trademark on a common english word... Even if he does run the company.
First, Apple's App Store policy has nothing to do whatsoever about trademarks. Everything about this app is based on tools provided by Apple, in a store run by Apple for use on a product that is made exclusively by Apple. It is totally at their discretion to allow or reject this app. They could have requested a name change.
Even if it's a coincidence that this title uses a common English word that happens to be the surname of the company's celebrity CEO and more famous co-founder (although Woz's "Dancing with the Stars' effort might change that ;) ), I can still see Apple not allowing it. (I can see Microsoft objecting to a firewall called Gates, or a crotch-kicking game called Ballmer.)
Apropos of nothing: Have you noticed that after Woz's "Dancing with the Stars" appearance, Apple's stock has shot up 10%? Hmmmm.
#6
Bjango
- Newbie
-
- Group: Members
- Posts: 5
- Joined: 25-November 08
Posted 11 March 2009 - 03:14 PM
Thank you very much for the review. We appreciate it!
---
"The application doesn’t provide a way to itemize expenses—a problem if you’re charging costs back to a client."
This would be a great feature. We plan to add it soon.
---
"And the use of a built-in mail client for data export, rather than the default Mail app on the iPhone or iPod touch, will be a problem for some users."
I agree that we don't have the perfect solution for this yet. Due to the fact that the iPhone's Mail client can't send attachments from 3rd party apps, we were faced with 3 options for exporting via email:
1. Include the information in the body text of the email and use the iPhone's Mail app. Not as easy to use: the user would need to copy+paste from the email into a new text file, then possibly rename it (.csv etc) before importing into their preferred desktop app. This would also have caused issues with large amounts of data, that probably wouldn't be able to be passed to Mail.
2. Include a full SMTP server in Jobs. This might have stopped us from being approved on the app store (duplicating functionality of Apple's in built apps is not allowed under the SDK). It also would have required the user to enter their email password in our app. Both of those things didn't seem like a good idea (we really don't want to know anyone's password for anything!).
3. Build a small webservice to send the email for us.
We went with option 3.
I know it doesn't seem ideal as is, but please be assured we don't keep anything at all. The data is just relayed. It's not kept.
I think we'll add Wi-Fi, browser based exporting in the future though. It'd solve a lot of potential issues.
---
Lots of new features are coming to Jobs and we welcome all feedback. Feel free to get in touch if there's anything you'd like added:
http://bjango.com/contact/
https://twitter.com/bjango
---
"The application doesn’t provide a way to itemize expenses—a problem if you’re charging costs back to a client."
This would be a great feature. We plan to add it soon.
---
"And the use of a built-in mail client for data export, rather than the default Mail app on the iPhone or iPod touch, will be a problem for some users."
I agree that we don't have the perfect solution for this yet. Due to the fact that the iPhone's Mail client can't send attachments from 3rd party apps, we were faced with 3 options for exporting via email:
1. Include the information in the body text of the email and use the iPhone's Mail app. Not as easy to use: the user would need to copy+paste from the email into a new text file, then possibly rename it (.csv etc) before importing into their preferred desktop app. This would also have caused issues with large amounts of data, that probably wouldn't be able to be passed to Mail.
2. Include a full SMTP server in Jobs. This might have stopped us from being approved on the app store (duplicating functionality of Apple's in built apps is not allowed under the SDK). It also would have required the user to enter their email password in our app. Both of those things didn't seem like a good idea (we really don't want to know anyone's password for anything!).
3. Build a small webservice to send the email for us.
We went with option 3.
I know it doesn't seem ideal as is, but please be assured we don't keep anything at all. The data is just relayed. It's not kept.
I think we'll add Wi-Fi, browser based exporting in the future though. It'd solve a lot of potential issues.
---
Lots of new features are coming to Jobs and we welcome all feedback. Feel free to get in touch if there's anything you'd like added:
http://bjango.com/contact/
https://twitter.com/bjango
Page 1 of 1
