I'm a junior dev and have an opportunity to develop a watch app version for an existing WeChat/Snapchat type of language learning/social iPhone app and being fairly fresh to development I have a few questions. My goal is to create a solid and very simple Version One watch app. The watch app will have basic glances such as:
Display most recent friend requests
Displaying recent favourited chat messages
Displaying recent favourited translation
User can send an emoji reply or speak a reply or defined canned responses
Display the 12 most recent chats represented by a small circle avatar of that buddy. User then clicks a buddy to send an emoji, canned response or audio message.
Questions
1. If you only want glances and you don’t want to create a full version watch app what do you do? Just let the iPhone Watch app handle the glances and notifications and simply create only a watch extension? Can an iPhone app send data to a watch to display a glance without creating a watch app? Glances still have to be set up via the iPhone Watch app right? Or with watchOS2 can glances be set up via watch directly (provided you created a watch app)?
2. How would I go about creating a login procedure for mock purposes if I temporarily don’t have access to the real server info? Would I use FireBase or Parse with a few fake user objects and then swap out the Parse code for the real server code later?
3. With watchOS2 the user doesn’t need the iPhone. The user will already have the iPhone version of the app. So should the user be logging in to their account via the watch or via the iPhone?
4. The iPhone app is written in Objective-C. This watch app will be written in Swift. Since it’s a watch app based on the iPhone app it’s obviously more simplified. If my glances and complications only involve user favourites, avatars etc and not full functioning app like the iPhone version how should I approach this?
5. Working remotely would the company expect me to mock it up via a 3rd party back-end first?
6. If they do give me their access to their user base and server data how do I manage this securely? I am working remotely so I’m not yet sure ho they will expect me to handle this. Of course we will discuss this but I’d like to hear from senior devs about this.
7. The company has all of the info I need of course. So should I recommend remote version control collaboration or should I ask them for what I need and work on my own?
8. This is just an initial presentation for the green light. What do you recommend for the least amount of stress? Don’t worry about all of the above and just present a Sketch Board?
9. As a junior dev what time frame should I give them? What is the usual time required for a basic watch app with basic glance features?
11. Should I be creating a new native app or a new target of the existing app? Which would be easier since the original iPhone app is a major app? It's written in Obj-C so that play a factor in my approach.
Display most recent friend requests
Displaying recent favourited chat messages
Displaying recent favourited translation
User can send an emoji reply or speak a reply or defined canned responses
Display the 12 most recent chats represented by a small circle avatar of that buddy. User then clicks a buddy to send an emoji, canned response or audio message.
Questions
1. If you only want glances and you don’t want to create a full version watch app what do you do? Just let the iPhone Watch app handle the glances and notifications and simply create only a watch extension? Can an iPhone app send data to a watch to display a glance without creating a watch app? Glances still have to be set up via the iPhone Watch app right? Or with watchOS2 can glances be set up via watch directly (provided you created a watch app)?
2. How would I go about creating a login procedure for mock purposes if I temporarily don’t have access to the real server info? Would I use FireBase or Parse with a few fake user objects and then swap out the Parse code for the real server code later?
3. With watchOS2 the user doesn’t need the iPhone. The user will already have the iPhone version of the app. So should the user be logging in to their account via the watch or via the iPhone?
4. The iPhone app is written in Objective-C. This watch app will be written in Swift. Since it’s a watch app based on the iPhone app it’s obviously more simplified. If my glances and complications only involve user favourites, avatars etc and not full functioning app like the iPhone version how should I approach this?
5. Working remotely would the company expect me to mock it up via a 3rd party back-end first?
6. If they do give me their access to their user base and server data how do I manage this securely? I am working remotely so I’m not yet sure ho they will expect me to handle this. Of course we will discuss this but I’d like to hear from senior devs about this.
7. The company has all of the info I need of course. So should I recommend remote version control collaboration or should I ask them for what I need and work on my own?
8. This is just an initial presentation for the green light. What do you recommend for the least amount of stress? Don’t worry about all of the above and just present a Sketch Board?
9. As a junior dev what time frame should I give them? What is the usual time required for a basic watch app with basic glance features?
11. Should I be creating a new native app or a new target of the existing app? Which would be easier since the original iPhone app is a major app? It's written in Obj-C so that play a factor in my approach.
Last edited: